Eagle Jet Charter Rockwell NA-265-80 accident
Rockwell NA-265-80 · Accident: airframe, component or system failure during landing
From Spirit of St Louis Airport (SUS) to Boston Logan International Airport (BOS)
Event
- NTSB case
- NYC02LA036
- 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
- Unknown
- 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
- Charter & commuter
- 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
Rockwell NA-265-80
- Aircraft type
- Rockwell NA-265
- 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
- N819GY
- Operator
- Eagle Jet Charter
- Onboard fatalities
- Unknown
- Route
- From Spirit of St Louis Airport (SUS), St. Louis, MOTo Boston Logan International Airport (BOS), Boston, MA
- 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 135: Air Taxi & Commuter
- 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
- Airframe, component or system failure
- 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
- Thrust reverser › Fatigue
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
After touchdown, the pilot deployed the thrust reversers and shortly thereafter, the airplane yawed violently to the right. The pilot maintained control, and the airplane came to a stop on the runway. Subsequent examination of the airplane revealed that the left engine thrust reverser assembly had separated from the engine and was found on the runway. Examination of the left thrust reverser outboard pinion gearbox revealed three fatigue bolts, with multiple origins. A fourth bolt was pulled completely out of the flange and was slightly bent. The inboard pinion gearbox was fractured into two parts and contained two regions of fatigue in the rails at the forward flange. The fatigue features were consistent with low stress high-cycle fatigue. The left thrust reverser was installed on May 7, 1996. It was not determined if the left thrust reverser attaching bolts were replaced at that time. At the time of the accident, the left thrust reverser had accumulated 8,275 total landings, and 2,560 landings since it was installed.
Probable cause
The failure of the left thrust reverser assembly due to fatigue.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC02LA036
- Event ID
- 20011226X02438
- Case number
- NYC02LA036
- 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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2001-12-10.
- API snapshot SHA-256: 9d2f906d402b6f11c5a221e6c77dda7e2ed83fd3b77a72603c36be17dd7976d8; retrieved 2026-09-18T16:07:34.205Z.