ENG07IA030 · Learjet 36 A
Learjet 36 A · Incident: loss of engine power during takeoff
From Bismarck Municipal Airport (KBIS) to Bismarck Municipal Airport (KBIS)
Event
- NTSB case
- ENG07IA030
- 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
- Incident
- 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
- Not recorded
Learjet 36 A
- Aircraft type
- Learjet 36
- 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
- N136DH
- Operator
- Intermap Technologies
- Onboard fatalities
- Unknown
- Route
- From Bismarck Municipal Airport (KBIS), Bismarck, NDTo Bismarck Municipal Airport (KBIS), Bismarck, ND
- 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
- 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
- Minor
Cause areas
- Compressor assembly, forward fan › Foreign object damage
- Object › Bird(s)
Approximate · Estimated position: the centre of Bismarck, ND, the place the record names. Not the accident site.
NTSB narrative
A Learjet 36A experienced a bird strike on the right hand engine during takeoff. One fan blade of the engine fractured below the mid-span and all others had tears on the leading edges.
Some of the liberated fan blade fragments were ejected through the engine fan case just forward of the fan containment ring in three different clocking locations. One fragment passed through the top portion of the oil tank, breaching it. Another ejected blade fragment penetrated the nacelle skin but neither was in the direction of the fuselage, thus limiting the damage only to the nacelle. The bird was identified as a male mallard duck.
Probable cause
A total loss of engine power during takeoff due to the right engine sustaining a fractured fan blade after the ingestion of a mallard duck. Some liberated fan blade fragments were uncontained, penetrating the nacelle.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ENG07IA030
- Event ID
- 20081219X65334
- Case number
- ENG07IA030
- 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 UTC date the NTSB stores; the local time zone is not recorded, so the local date may differ by a day.
- API snapshot SHA-256: 40310209b7581b6cfc9f777faf042b5ebbadb262abf741c25221355fd9382445; retrieved 2026-09-22T03:46:58.411Z.