NYC83FA249 · Gates Learjet 35A
Gates Learjet 35A · Accident: overrun during landing
From Allegheny County Airport (AGC) to an unrecorded destination
Event
- NTSB case
- NYC83FA249
- 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
Gates Learjet 35A
- Aircraft type
- Learjet 35
- 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
- N780A
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Allegheny County Airport (AGC), West Mifflin, PATo not recorded
- 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 › Aborted landing, not performed
- Pilot in command › Airspeed, misjudged
- Pilot in command › Distance, misjudged
- Pilot in command › Go-around, not selected
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
PASSENGERS DESCRIBED TOUCHDOWN AS FAST & LONG WITH NO ENG NOISE ASSOCIATED WITH REVERSE THRUST IMMEDIATELY AFTER TOUCHDOWN. THE ACFT RAN OFF THE END OF THE RWY & THE NOSE GEAR SEPARATED. ACCORDING TO THE CREW THE PLT INITIATED THE THRUST REVERSERS AFTER TOUCHDOWN, HOWEVER, THE PINS DID NOT REMOVE & THE THRUST LEVERS WERE RESTORED. AS BRAKING WAS EMPLOYED, THE THRUST REVERSERS WERE RE-INITIATED. THE PINS REMOVED & FULL REVERSE WAS APPLIED. BY THIS TIME THERE WAS INSUFFICIENT RWY REMAINING TO INITIATE A GO-AROUND. THE SQUAT SWITCH RELAY PANEL PREVENTS OPERATION OF THE THRUST REVERSER SYSTEM UNTIL THE SQUAT SWITCHES ARE IN THE GROUND MODE. THE GROUND SPOILERS WERE NOT DEPLOYED.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record NYC83FA249
- Event ID
- 20001214X44665
- Case number
- NYC83FA249
- 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: 60c7dd9a992d45d05a28badc58d7c1e3c0cb067ee379c94d613c101f7cbcba77; retrieved 2026-09-22T02:28:53.442Z.