NYC99FA091 · Raytheon Corporate Jets BE-400A
Raytheon Corporate Jets BE-400A · Accident: overrun during landing
From PBI · West Palm Beach, FL to Raleigh County Memorial Airport (BKW)
Event
- NTSB case
- NYC99FA091
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- 0
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Raytheon Corporate Jets BE-400A
- Aircraft type
- Raytheon Corporate Jets BE-400
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N400VG
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From PBI · West Palm Beach, FLTo Raleigh County Memorial Airport (BKW)
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Landing · landing roll
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Overrun
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Pilot in command › Airspeed, misjudged
- Pilot in command › Altitude, misjudged
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The airplane touched down about 1/3 beyond the approach end of Runway 28, a 5,000 foot-long, asphalt runway. The PIC stated, 'as usual,' he applied 'light' braking and attempted to actuated the airplane's thrust reverser (TR) system; however, the TR handles could not be moved beyond the 'Deploy-Reverse-Idle' position. After the PIC cycled the levers two or three times, he began to apply maximum braking. A passenger in the airplane stated he looked out of the cockpit window, saw the end of the runway, and the airplane seemed like it was still moving 'pretty fast.' As the airplane approached the end of the runway, he could see smoke, which he believed was coming from the airplane's tires. He then sensed the airplane was falling. The co-pilot stated he had no memory at all of the accident flight. Review of the CVR revealed the co-pilot said that the airplane was 'Vref plus about twenty,' when the airplane was 100 feet over the runway threshold. The PIC could not recall the airplane's touchdown speed, however, he stated that it seemed like the airplane was still traveling 50 to 60 knots when it departed the end of the runway. A pair of parallel tire marks were observed 3,200 feet beyond the approach end of the runway. The tire marks extended past the end of the runway and onto a 106 foot-long grass area. The airplane came to rest on a plateau about 90 feet below the runway elevation. Examination of the airplane, including the optional TR system did not reveal any pre-impact malfunctions. The airplane's estimated landing distance was calculated to be about 3,100 feet. The PIC reported about 4,700 hours of total flight experience, of which, 107 hours were in make and model. The PIC stated he had never performed a landing in the accident airplane without using the TR system. Winds reported at the time of the accident were from 290 degrees at 15 knots, with 21 knot gusts.
Probable cause
The pilot-in-command misjudged his altitude and airspeed which resulted in an overrun. Contributing to the accident were the pilot's lack of total flight experience in make and model, the pilot's reliance on the airplane's optional thrust reverser system and his inability to engage the airplane's thrust reverser system for undetermined reasons.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC99FA091
- Event ID
- 20001205X00546
- Case number
- NYC99FA091
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: d70219158676ce2f54147693c0703ac11cf93a64706801abc88cd62610cc968e; retrieved 2026-09-21T11:08:58.086Z.