Raytheon 400A accident near Fernandina Beach, Florida, November 1, 2020
On November 1, 2020 at about 7:00 pm local time, a 2003 Raytheon 400A, registered N456FL, was substantially damaged in an accident during landing (landing roll) near Fernandina Beach, Florida (Fernandina Beach Municipal Air airport). It was an other work-use flight under charter and air-taxi rules (Part 135). 1 person had minor injuries; 5 others were unhurt. The weather was instrument conditions (cloud, fog or low visibility).
The NTSB's probable cause their words, unchanged
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.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- November 1, 2020 · about 7:00 pm local time
- Place
- Fernandina Beach, Florida · Fernandina Beach Municipal Air · map
- Type
- Accident
- Injuries
- 1 person had minor injuries; 5 others were unhurt.
- Weather
- instrument conditions (cloud, fog or low visibility)
- Aircraft
- Raytheon 400A, built 2003
- Registration
- N456FL · no longer on the register · serial RK-365
- Damage
- Substantial damage
- Flight
- Other work-use flight · charter and air-taxi rules (Part 135)
The NTSB's narrative final · quoted from the NTSB record
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.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Runway excursion during landing (landing roll) defining event
- Other weather encounter during landing
The NTSB's findings
- Environmental issues › Conditions/weather/phenomena › Wind › Tailwind › Response/compensation
- Environmental issues › Physical environment › Runway/land/takeoff/taxi surface › Wet surface › Decision related to condition
- Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Flight crew
- Aircraft › Aircraft oper/perf/capability › Aircraft capability › Landing distance › Not attained/maintained
- Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Surface speed/braking › Not attained/maintained
- Personnel issues › Action/decision › Action › Incorrect action performance › Copilot
- Personnel issues › Action/decision › Action › Incorrect action performance › Pilot
Pilot
- Certificate: airline transport pilot, commercial pilot
- Ratings: multi-engine land; single-engine land; instrument: airplane
- Flight time: 3,445 hours in all; 526 in this make and model; 84 in the last 90 days; 42 in the last 30 days; 1,595 as pilot in command
- Last flight review: June 16, 2020
- Medical certificate: Class 1 (without waivers/limitations)
- Seat: left
- Injury: minor injuries
Co-pilot
- Certificate: airline transport pilot, commercial pilot
- Ratings: multi-engine land; single-engine land; instrument: airplane
- Flight time: 6,850 hours in all; 300 in this make and model; 85 in the last 90 days; 42 in the last 30 days; 4,500 as pilot in command
- Last flight review: March 17, 2020
- Medical certificate: Class 1 (with waivers/limitations)
- Seat: rgt
- Injury: no injuries
Passenger
- Seat: left
Passenger
- Seat: rgt
Passenger
- Seat: left
- Injury: minor injuries
Passenger
- Seat: rgt
The aircraft
- Airframe total time: 8,760.9 hours
- Last inspection: continuous airworthiness programme, June 30, 2018
- Maximum gross weight: 16,400 lb
- Seats: 10
- Landing gear: retractable
- Engine 1: Williams International FJ44-3AP (turbofan); 2,614 hours total
- Engine 2: Williams International FJ44-3AP (turbofan); 2,614 hours total
- Operator: Georgia Jet Inc.
The flight
- Departed from: APF Naples FL at 5:04 pm
- Flight plan: IFR
- Runway 13, 5,152 ft by 100 ft
- A second pilot was aboard
Weather at the time
- Light: daylight
- Wind: from 290° at 17 knots, gusting 23
- Visibility: 1.2 statute miles
- Sky: broken clouds at 1,300 ft
- Temperature: 73°F (23°C), dew point 73°F (23°C)
- Altimeter: 30.06 inHg
- Observation at 2:00 pm from FHB
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 2 | |||
| Passengers | 1 | 3 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
32 documents, released by the NTSB on November 18, 2022. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
