IAD01LA022 · Learjet 35
Learjet 35 · Accident: overrun during takeoff
From Schenectady County Airport (SCH) to LaGuardia Airport (LGA)
Event
- NTSB case
- IAD01LA022
- 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
- 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
Learjet 35
- 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
- N435JL
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Schenectady County Airport (SCH), Schenectady, NYTo LaGuardia Airport (LGA), New York, NY
- 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
- Takeoff · rejected takeoff
- 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 › Trim setting, improper
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The captain stated that prior to departure the flight controls were tested, with no abnormalities noted, and the takeoff trim was set to the "middle of the takeoff range," without referring to any available pitch trim charts. During the takeoff roll, the pilot attempted to rotate the airplane twice, and then aborted the takeoff halfway down the 4,840 foot long runway, because the controls "didn't feel right." The airplane traveled off the departure end of the runway and through a fence, and came to rest near a road. The pilot reported no particular malfunction with the airplane. Examination of the airplane revealed that the horizontal stabilizer was positioned at -4.6 degrees, the maximum nose down limit within the takeoff range. The horizontal stabilizer trim and elevator controls were checked, and moved freely through their full ranges of travel. According to the AFM TAKEOFF TRIM C.G. FUNCTION chart, a horizontal stabilizer trim setting of -7.2 was appropriate with the calculated C.G. of 20% MAC. Additionally, Learjet certification testing data stated that the pull force required at a trim setting of -6.0 degrees, the "middle of the takeoff range", was 33 pounds. With the trim set at the full nose down position (-1.7 degrees), 132 pounds of force was required.
Probable cause
The pilot's improper trim setting, which resulted in a runway overrun and impact with a fence.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record IAD01LA022
- Event ID
- 20010126X00361
- Case number
- IAD01LA022
- 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, coordinates. 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: 81530799db83558f8042b96164e220d71043666edf69c28dbd9af6a57e90f835; retrieved 2026-09-22T12:15:01.032Z.