Narrative:

I was the pilot flying when our B737-700; ingested a goose that was on the runway with a flock of geese; into the left (number 1) engine at/approaching V1. We continued the takeoff roll and rotation with nearly immediate compressor stalls/surges coming from the engine. Tower reported smoke and flames coming from the left engine within the first several hundred feet of flight. I swapped controls with the captain when safely airborne at approximately 1;000 AGL; cleaned up the aircraft; and executed the engine fire/severe damage/separation/seizure checklist immediate action items. At no time did we have any associated warning/caution lights or warning horn and the engine kept running with nearly symmetrical power until we shut the engine down in accordance with the checklist. After accomplishing the engine shutdown; I declared an emergency with tower; was given a block altitude; and we leveled off at approximately 5;000 MSL and 210 KTS and stayed up tower frequency receiving radar vectors to remain within tower airspace while accomplishing the rest of the checklist. Once completed; we swapped controls while the captain explained the situation to the flight attendants as well as made a PA to the passengers. We then re-swapped controls and executed the one-engine inoperative landing checklist; calculated flaps 15 single-engine landing data; reviewed the approach and go-around procedure; and set-up and executed a fairly uneventful single-engine approach and landing. Fire and rescue personnel met us on the runway and told us the engine looked safe to taxi to the gate. We then reviewed brake cooling data; with no special procedures required; and taxied uneventfully to the gate to offload the passengers and secure the aircraft. I discussed the incident with the airfield operations representative after we returned to the gate and he said they are constantly battling to keep the migrating snow geese clear of the runway environment on the airfield. Potentially this event will lead to increased awareness and funding for the bash program and they will have sufficient manning and equipment to increase bird detection capability and reduce the likelihood of bird strikes in the future.

Related reports:

Google
 

Original NASA ASRS Text

Title: B737 flight crew reports ingesting a goose at V1 during takeoff with the First Officer flying. Loud compressor stalls are heard from the left engine and the Captain assumes control at approximately 100 FT AGL but the positive rate call is not made and the gear is not retracted. After the engine is shut down the gear is noticed and retracted. Flight returns for a single engine landing.

Narrative: I was the pilot flying when our B737-700; ingested a goose that was on the runway with a flock of geese; into the left (Number 1) Engine at/approaching V1. We continued the takeoff roll and rotation with nearly immediate compressor stalls/surges coming from the engine. Tower reported smoke and flames coming from the left engine within the first several hundred feet of flight. I swapped controls with the Captain when safely airborne at approximately 1;000 AGL; cleaned up the aircraft; and executed the Engine Fire/Severe Damage/Separation/Seizure Checklist immediate action items. At no time did we have any associated warning/caution lights or warning horn and the engine kept running with nearly symmetrical power until we shut the engine down in accordance with the checklist. After accomplishing the engine shutdown; I declared an emergency with Tower; was given a block altitude; and we leveled off at approximately 5;000 MSL and 210 KTS and stayed up Tower frequency receiving radar vectors to remain within Tower airspace while accomplishing the rest of the checklist. Once completed; we swapped controls while the Captain explained the situation to the flight attendants as well as made a PA to the passengers. We then re-swapped controls and executed the One-Engine Inoperative Landing Checklist; calculated Flaps 15 single-engine landing data; reviewed the approach and go-around procedure; and set-up and executed a fairly uneventful single-engine approach and landing. Fire and rescue personnel met us on the runway and told us the engine looked safe to taxi to the gate. We then reviewed brake cooling data; with no special procedures required; and taxied uneventfully to the gate to offload the passengers and secure the aircraft. I discussed the incident with the Airfield Operations representative after we returned to the gate and he said they are constantly battling to keep the migrating Snow Geese clear of the runway environment on the airfield. Potentially this event will lead to increased awareness and funding for the BASH Program and they will have sufficient manning and equipment to increase bird detection capability and reduce the likelihood of bird strikes in the future.

Data retrieved from NASA's ASRS site as of July 2013 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.