Beechcraft 400A N456FL
1 November 2020 · Fernandina Beach, Florida, United States · Minor injuries
Summary
On 1 November 2020 at about 19:00 local time, a Beechcraft 400A registered N456FL, operated by Georgia Jet Inc., was involved in an accident near Fernandina Beach, Florida, United States. 6 people were on board and one had minor injuries. The aircraft was substantially damaged. The NTSB has published a probable cause for this accident; it is quoted in full below.
The record
- Date
- at 19:00
- Classification
- Accident
- Location
- Fernandina Beach, Florida, United States
- Nearest airport
- Fernandina Beach Municipal Air (FHB)
- Coordinates
- 30.6118, -81.4612
- Aircraft
- Beechcraft 400A
- Registration
- N456FL
- Category
- Airplane
- Year built
- 2003
- Engines
- 2
- Operator
- Georgia Jet Inc.
- Operating rule
- Part 135: Air Taxi & Commuter
- Purpose of flight
- Other Work Use
- Phase of flight
- Not recorded
- Route
- Naples → Unknown
- Aircraft damage
- Substantial
- Weather
- IMC
- Light
- Day
- NTSB number
- ERA21LA036
People
1 person had minor injuries.
| On board | Died | Serious | Minor | Uninjured |
|---|---|---|---|---|
| 6 | 0 | 0 | 1 | 5 |
Probable cause
The flight crew's improper decision to land with a tailwind on a wet runway, which resulted in a runway overrun. Contributing to the accident was the copilot’s early retraction of the speed brakes and the pilot’s decision to turn off the anti-skid system.
Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.
Read the full NTSB narrative
The air taxi flight departed in visual meteorological conditions. Upon arrival in the area of the destination airport, the flight crew of the business jet encountered instrument meteorological conditions and precipitation as a trough passed through the area. During the downwind leg of the instrument approach to runway 13, the copilot checked the automated surface-reported wind, which was from 110° at 4 knots gusting to 18 knots. Audio from the airplane’s cockpit voice recorder showed that, as the crew continued the approach, the copilot twice commented to the pilot that the actual wind for the approach was a tailwind (which he likely observed on the airplane’s primary/multi-function displays), at one point noting that the tailwind was more than 20 knots. The flight crew nonetheless continued the instrument approach, and after visually identifying the runway at a height of about 300 feet above the ground, landed the airplane. Data downloaded from the airplane’s flight data recorder showed that the airplane touched down at a groundspeed exceeding 120 knots, about 10 knots faster than the airplane’s reference approach airspeed (Vref). After the airplane touched down, the pilot believed that there was a problem with the airplane’s brakes, as he received “zero feedback” despite his attempts to slow down. During the landing the copilot deployed the airplane’s speed brakes for about 6 seconds before retracting them, about the time he commented to the pilot that they should abort the landing. The pilot declined to abort and directed the copilot to deactivate the airplane’s anti-skid system with about 1/3 of the available runway remaining. With no observed change in the airplane’s braking, the pilot attempted to slow the airplane by steering it from side to side on the runway, but it ultimately the airplane departed the end of the runway. The airplane came to rest in the soft soil and grass about 150 feet beyond the runway end, substantially damaging the wings and fuselage during the excursion. After the accident, the pilot observed that the runway was wet, but that there was no standing water. Postaccident examination and testing of the airplane’s braking system revealed no evidence of any preaccident mechanical malfunctions or failures. Review of recorded weather information, and a witness who landed shortly after the accident flight, confirmed that after the flight crew reported obtaining the wind from the automated weather reporting system at the airport and during their final approach to the runway, the wind had shifted from a slight headwind out of the southeast to a substantial tailwind out of the northwest. Based on the comments made by the copilot during the approach, the flight crew was aware of this tailwind condition, but did not discontinue their approach in favor of landing in the opposite direction, where a headwind would have prevailed. Landing overruns typically involve multiple cumulative factors, and may include a wet runway, landing with a tailwind, and the improper use of deceleration devices. During the accident sequence, the copilot mentioned twice the presence of a tailwind, and flight data recorder information indicated that the airplane’s groundspeed was higher than normal at touchdown. Thus, the pilots failed to recognize and take action in response to performance cues that indicated that the airplane would be landing with a significant tailwind. While the flight crew had accounted for the wet runway in their preflight performance calculations, the premature stowing of the speed brakes after touchdown prevented lift from being further decreased, which would have increased the weight on the airplane’s main wheels, thereby increasing braking effectiveness. In addition, turning off the anti-skid system precluded protection from skids and likely resulted in a longer landing roll along the wet runway. In summary, the flight crew should not have attempted the landing given the prevailing wind, and their actions further exacerbated the situation when they retracted the speed brakes early and turned off the anti-skid system. This resulted in the pilots’ inability to stop the airplane on the available runway surface and the subsequent runway overrun.
Quoted verbatim from the NTSB record.
Other Beechcraft 400 accidents
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 22 Jul 2020 | Beechcraft 400 | Montgomery, Alabama, United States | N425BJ LLC | No injuries | - |
| 14 Sep 2021 | Beechcraft 400A | Charleston, South Carolina, United States | Aircraft Management Group | No injuries | - |
| 11 Feb 2019 | Beechcraft 400 | Richmond, Indiana, United States | Stein's Aircraft Services, LLC | No injuries | - |
| 5 Feb 2018 | Beechcraft 400A | Cleveland, Ohio, United States | Travel Management, Inc | No injuries | - |
| 2 May 2018 | Beechcraft 400 | Geneva, Switzerland | Flairjet Ltd | No injuries | - |
| 15 Jul 2022 | Beechcraft 400A | Brunswick, Georgia, United States | Aircraft Mgt. Group, Inc | No injuries | - |
Other accidents in this area
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 19 Aug 2020 | Piper PA32 | Tallahassee, Florida, United States | - | Minor injuries | - |
| 25 Jun 2020 | Bell 206 | Coconut Creek, Florida, United States | Hmc Lift Llc | Serious injuries | - |
| 15 Jun 2020 | Piper PA46 | Williston, Florida, United States | - | No injuries | - |
| 3 May 2020 | Airbus Helicopters AS350 | Clewiston, Florida, United States | MacNeil Aviation LLC | No injuries | - |
| 30 Jan 2020 | Piper PA28 | Naples, Florida, United States | Apflight Llc | No injuries | - |
| 31 Dec 2020 | Cessna 501 | Opa Locka, Florida, United States | Interstellar Air LLC | No injuries | - |