ENG07IA030

NTSB incident investigation · Learjet 36 · Bismarck, ND · June 4, 2007

Incident · No injuriesIncident investigationFinal report
Date
June 4, 2007
Place
Bismarck, ND
Injuries
2 uninjured
Damage
Minor damage
Phase of flight
Takeoff
Aircraft
N136DHLearjet 36
Status
Completed · report March 16, 2011
Report
Approved by Office Director
NTSB office
Aviation Engineering Division
Case key
66032

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the incident.

On this page

Probable cause

The NTSB’s determination of the probable cause, and any contributing factors.

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.

Analysis

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.

Factual narrative

The factual narrative625 words

On May 4, 2007, at approximately 1030z (0530 local), a Learjet 36A,registration number N136DH, equipped with two Honeywell TFE731-2-2B turbofan engines, ingested a bird in the right engine while accelerating for takeoff at the Bismarck Municipal Airport (KBIS). The takeoff was aborted at about 110-120 knots and the airplane was brought to an uneventful stop. The airplane’s drag chute was deployed and moderate braking was necessary to get the airplane stopped. Approximately 2,000 feet of runway remained when the airplane taxied off the runway and on to the taxi way. Once the airplane was off the runway, the crew scanned the engine instruments and annunciators. The engine instruments appeared normal and the right engine fuel computer annunciator was illuminated. As the power levers were advanced to taxi, the right engine fuel flow fluctuated erratically and crew felt a vibration so the right engine was shut down. The vibrations stopped and the aircraft was taxied to the FBO uneventfully on one engine. The crew reported that they did not see the bird strike the airplane but described the engine event ‘a loud pop like the sound of a compressor stall and then a vibration in the whole airframe with a slight pull to the right’. The flight, operated under the provisions of Title 14 CFR Part 91, was a local flight intending to perform geophysical mapping. It was the first flight of the day for this aircraft. No injuries were reported by the two crewmembers.

The post flight inspection report indicated that blood was found along the right engine cowling and along the right side of the fuselage. Approximately one quarter of the retaining rivets on the forward engine inlet cowling were sheared or popped. There was a 3 inch gash in the right outboard cowling above the oil filler port and the aft cowling was perforated and scored. A second blade fragment penetrated the nacelle skin but none of fan blade exit trajectories were in the direction of the fuselage, thus limiting the damage only to the nacelle. No damage was noted to the engine pylon, fuselage, or surrounding wing and flaps.

The airport authority conducted a runway foreign object check and found the head of a mallard duck on the runway. No other debris was found. A Bird Strike report was filed with the FAA and sent to the Office of Airport Safety and Standards AAS-310.

Inspection of the right hand engine revealed that one fan blade was fractured below the mid-span and was missing approximately one half of its material. Eight other blades had lost segments of their leading edge corners while all others had tears on the leading edges. Some of the liberated fragments were ejected through the engine fan case just forward of the fan containment ring in three different clocking locations. There was damage and perforations to the low pressure and high pressure bleed air lines. One fragment passed through the top portion of the oil tank, breaching it. The dimension of the largest penetration in the fan case was 7 inches by 1.5 inches. Visual examination by the NTSB material laboratory of the remaining fracture surfaces of the fan blades revealed no preexisting fatigue-type mechanism and all the fractures were consistent with overstress.

Bird remains were forwarded to the Smithsonian Institution who identified them as a male Mallard Duck (Anas Platyrhynchos). The average weight of this species is 1,100 grams. The strike information was entered into the FAA Wildlife Strike database.

Although the weight of an average duck is known, it was not possible to estimate the quantity ingested by the engine because remains of the duck were found smeared on the outside of the nacelle indicting that only a part of the duck was ingested into the engine.

Sequence of events

NTSB’s coding before 2008: each occurrence and phase of flight, and the causes and factors under it. The codes are defined in NTSB’s coding manual.

Loss of engine powerTakeoff - aborted
Compressor assembly,forward fan - foreign object damageCause
Object - bird(s)Cause
Misc,engine uncontained failure - foreign object damageFactor

Aircraft

Registration
N136DH
Reported as
Learjet 36 (A)
Category
Airplane
Serial number
36-036
Engines
Garrett TFE731, 3,500 lbs thrust, turbo fanGarrett TFE731, 3,500 lbs thrust, turbo fan
Damage
Minor damage
Flight
Business · Part 91
Operator
Intermap Technologies
Registered owner
Intermap Technologies
Airworthiness certificate
Standard, Transport
Departed
KBIS · Bismarck, ND
Destination
KBIS · Bismarck, ND
Flight plan
Unknown
Airport
KBIS · Bismarck

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Docket · 2

The files NTSB released with the investigation on March 16, 2011, on NTSB’s docket system: statements, records, photos and specialists’ reports. 2.8 MB in all.