Multi-Aero Learjet 24D accident
Learjet 24D · Accident: loss of engine power during initial climb
From CPS · St. Louis, MO to North Platte Regional Airport Lee Bird Field (LBF)
Event
- NTSB case
- CHI04FA029
- 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
Learjet 24D
- Aircraft type
- Learjet 24
- 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
- N77JL
- Operator
- Multi-Aero
- Onboard fatalities
- Unknown
- Route
- From CPS · St. Louis, MOTo North Platte Regional Airport Lee Bird Field (LBF), North Platte, NE
- 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
- 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 engine power
- 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
- All engines › Failure
- Object › Bird(s)
- Ram/induction air › Impeded
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
!!THIS CASE WAS MODIFIED JANUARY 12, 2006!!
The turbojet airplane was destroyed during a forced landing and post accident fire after a loss of power in both engines during takeoff climb. The pilot reported that both engines operated normally during taxi and pre-takeoff checks. He reported that, "We rotated positive rate gear up, V2 plus 30 flaps up, and at that point we struck birds taking No. 2 engine out. Upon losing No. 2 engine I advanced thrust levers forward and realized that the No. 1 engine was only producing approximately 70% RPM with EGT over read line." He executed a forced landing to a field and the crew and passengers evacuated the burning airplane. The copilot reported, "At approximately 500 to 1,000 ft. above ground level, I observed a large flock of birds straight ahead of us, and then passing just off our nose to the left side. I immediately heard an engine flameout. As I started to go to the checklist for single engine operations, I quickly realized that we were loosing airspeed and unable to maintain altitude. The PIC said we were going down and heading for the best emergency-landing stop." The Cockpit Voice Recorder (CVR) recorded the pilot stating, "We hit a bird," and the copilot stating, "Yep," immediately following the CVR recording a "sound similar to decrease in engine RPM." The inspection of the airplane's fuel system, pneumatic system, engines, fuel controls and fuel pumps revealed no pre-impact anomaly. No physical evidence of bird ingestion was found in either engine. A CVR sound spectrum plot and a flight profile analysis revealed that one engine flamed out almost immediately after the sound of a "thump" on the CVR. The other engine's speed decreased and experienced stalls until the engine speed was reduced to flight idle. The original engine certification tests indicated that compressor stalls occurred when a 2-4 ounce starling was shot ingested into the engine, but physical damage from bird ingestion was very slight due to the all steel construction and geometry of the engine. Engine flameouts, however, were not recorded during the certification tests. A wildlife specialist conducted a bird count at the accident airport two days after the accident occurred, and he reported counting a flock of about 800 European Starlings.
Probable cause
The total loss of power to the right engine and the partial loss of power to the left engine after the airplane encountered a flock of birds during initial climb out, resulting in impeded ram induction airflow.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI04FA029
- Event ID
- 20031118X01915
- Case number
- CHI04FA029
- 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: 67d252ffcb54e5867d41a487b2a58aa516bd3992db676ae52f05f2d2abe1c433; retrieved 2026-09-18T15:36:28.625Z.