IAD02FA018 · Gates Learjet 25B
Gates Learjet 25B · Accident: loss of control in flight during initial climb
From Pittsburgh International Airport (PIT) to Boca Raton Airport (BCT)
Event
- NTSB case
- IAD02FA018
- 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
- 2 · 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
Gates Learjet 25B
- Aircraft type
- Learjet 25
- 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
- N5UJ
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Pittsburgh International Airport (PIT), Pittsburgh, PATo Boca Raton Airport (BCT), Boca Raton, FL
- 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
- Initial climb
- 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
- Loss of control in flight
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Remedial action, inadequate
- Unknown › Directional control, not maintained
- Unknown › Rotation, excessive
- Unknown › Rotation, premature
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
A commercial pilot, who observed the airplane during the takeoff attempt, stated that it used "lots" of runway, and that the nose lifted "too early and way too slow." The airplane "struggled" to get in the air, and it appeared tail heavy, with "extreme" pitch, about 45 degrees nose-up. It also appeared that the only thing keeping the nose up was ground effect. The airplane became airborne for "a very short time," then sank to the ground, and veered off the left side of the runway. The nose was "up" the whole time, the airplane never "rolled off on a wing," and the wings never wobbled. The engines were "really loud," like a "shriek," and engine noise was "continuous until impact." Another witness at a different location confirmed the extreme nose-high takeoff attitude and the brief time the airplane was airborne. It seemed odd to him that an airplane with that much power used so much runway. A runway inspection revealed no evidence of foreign objects or aircraft debris. Tire tracks from the airplane's main landing gear veered off the left side of the paved surface, at a 20-degree angle, about 3,645 feet from the runway's approach end. They continued for about 775 feet, then turned back to parallel the runway for another 650 feet, before ending about 50 feet prior to a chain link fence. There was no evidence that the nose wheel was on the ground prior to the fence. The fence, which was about 1,300 feet along the airplane's off-runway ground track and 200 feet to the left of the runway edge stripe, was bent over in the direction of travel. Ground scars began about 150 feet beyond the fence, and the main wreckage came to rest 300 feet beyond the beginning of the ground scars. The first officer advised a witness that he'd be making the takeoff; however, the pilot at the controls during the accident sequence could not be confirmed. When asked prior to the flight if he'd be making a high-performance takeoff, the captain replied that he didn't know. There was no evidence of mechanical malfunction.
Probable cause
The (undetermined) pilot-at-the-controls' early, and over rotation of the airplane's nose during the takeoff attempt, and his failure to maintain directional control. Also causal, was the captain's inadequate remedial action, both during the takeoff attempt and after the airplane departed the runway.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record IAD02FA018
- Event ID
- 20011202X02328
- Case number
- IAD02FA018
- 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: 6c1fc7ab163d90e2b9f8534e0ecdba1514ee8ef3dafdced5a4518af5003c58df; retrieved 2026-09-20T20:16:56.212Z.