 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Crew rejected the takeoff at low speed when the takeoff warning horn activated. Pilot attributes the flight crew's failure to configure the aircraft correctly and complete the before takeoff checklist to fatigue due to scheduling changes.
| Attributes | |
| ACN | 1258955 |
| Time | |
| Date | 201505 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | SWF.Airport |
| State Reference | NY |
| Environment | |
| Flight Conditions | VMC |
| Aircraft 1 | |
| Make Model Name | Large Transport |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Takeoff |
| Flight Plan | IFR |
| Person 1 | |
| Function | First Officer |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Events | |
| Anomaly | Deviation - Procedural Published Material / Policy |
Narrative:
Takeoff warning sounded on takeoff roll. Very low speed reject; taxied back for takeoff after realizing we had not configured for takeoff or ran the before takeoff checklist.extreme fatigue. I was scheduled for a 37 hour layover. That would have helped recover from prior sleep deprivation. Instead; crew scheduling revised my pairing after I showed at the jet in san diego. Instead of one leg to a long layover; they hub turned me into two legs. I had less than an hour at first stop. No time for a nap; food etc. Felt ok in bound; but was mildly fatigued at pushback for second leg. Was extremely fatigued upon arrival with one more leg to go. Stop crew scheduling from revisions of this nature. Just because it's 'legal' doesn't make it safe. Crew scheduling should schedule with safety in mind first; and system reliability second. 'Smart' scheduling would error on the side of safety and not fall into the 'it's legal therefore it's safe' mentality that seems to prevail currently. On the personal side; I should have called in fatigued in at the first stop. In the future I will call in fatigued when faced with similar circumstances.
Original NASA ASRS Text
Title: Crew rejected the takeoff at low speed when the takeoff warning horn activated. Pilot attributes the flight crew's failure to configure the aircraft correctly and complete the Before Takeoff Checklist to fatigue due to scheduling changes.
Narrative: Takeoff warning sounded on takeoff roll. Very low speed Reject; taxied back for takeoff after realizing we had not configured for takeoff or ran the before takeoff checklist.Extreme fatigue. I was scheduled for a 37 hour layover. That would have helped recover from prior sleep deprivation. Instead; crew scheduling revised my pairing after I showed at the jet in San Diego. Instead of one leg to a long layover; they hub turned me into two legs. I had less than an hour at first stop. No time for a nap; food etc. Felt ok in bound; but was mildly fatigued at pushback for second leg. Was extremely fatigued upon arrival with one more leg to go. Stop crew scheduling from revisions of this nature. Just because it's 'legal' doesn't make it safe. Crew scheduling should schedule with safety in mind first; and system reliability second. 'Smart' scheduling would error on the side of safety and not fall into the 'it's legal therefore it's safe' mentality that seems to prevail currently. On the personal side; I should have called in fatigued in at the first stop. In the future I will call in fatigued when faced with similar circumstances.
Data retrieved from NASA's ASRS site 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.