 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
An SF340 flight crew suffered multiple bird strike at rotation.
| Attributes | |
| ACN | 902087 |
| Time | |
| Date | 201007 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | ZZZ.Airport |
| State Reference | US |
| Aircraft 1 | |
| Make Model Name | SF 340B |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Takeoff |
| Flight Plan | IFR |
| Person 1 | |
| Function | Pilot Flying First Officer |
| Qualification | Flight Crew Commercial |
| Experience | Flight Crew Last 90 Days 46 Flight Crew Total 3000 Flight Crew Type 1800 |
| Person 2 | |
| Function | Pilot Not Flying Captain |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Events | |
| Anomaly | Inflight Event / Encounter Bird / Animal |
Narrative:
On the takeoff roll; after 80 KTS and just before V1; we identified a flock of seagulls on the runway. As we approached the birds and reached V1 I made a conscious effort to fly the takeoff per the standard profile. Impact occured near the time of rotation. The captain verbalized the check of all engine indications resulted in no abnormalities. I flew a standard take-off profile. The captain made the initial radio call to check in with center and then I took radio #1. The captain then tried to reach airport operations unsuccessfully; then checked the fom for its bird strike guidance. We discussed the situation and due to any lack of flight abnormalities decided to continue to our destination.the bird strike occurred because visibility of any objects that may have been on the runway was greatly reduced by both the curve of the runway and shimmering heat rising off of its surface. By the time the birds came into sight we were at a speed that would have required a high speed abort and would have incurred the risk associated with that maneuver.
Original NASA ASRS Text
Title: An SF340 flight crew suffered multiple bird strike at rotation.
Narrative: On the takeoff roll; after 80 KTS and just before V1; we identified a flock of seagulls on the runway. As we approached the birds and reached V1 I made a conscious effort to fly the takeoff per the standard profile. Impact occured near the time of rotation. The Captain verbalized the check of all engine indications resulted in no abnormalities. I flew a standard take-off profile. The Captain made the initial radio call to check in with center and then I took radio #1. The Captain then tried to reach Airport Operations unsuccessfully; then checked the FOM for its bird strike guidance. We discussed the situation and due to any lack of flight abnormalities decided to continue to our destination.The bird strike occurred because visibility of any objects that may have been on the runway was greatly reduced by both the curve of the runway and shimmering heat rising off of its surface. By the time the birds came into sight we were at a speed that would have required a high speed abort and would have incurred the risk associated with that maneuver.
Data retrieved from NASA's ASRS site as of April 2012 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.