37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 953630 |
Time | |
Date | 201106 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | MHTG.Tower |
State Reference | FO |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | B757-200 |
Operating Under FAR Part | Part 121 |
Flight Phase | Takeoff |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | B737 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | Landing |
Person 1 | |
Function | Captain Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Person 2 | |
Function | First Officer Pilot Not Flying |
Events | |
Anomaly | ATC Issue All Types |
Narrative:
On push back; mhtg ground control informed us of a runway change from runway 02 to runway 20. We were unable due to runway limited take off weight and requested runway 02 with 5 KTS tailwind. This required several transmissions back and forth with ground control while we requested a new flight plan and manually re-calculated take off data for a flaps 20 take off with 5 KTS tailwind. Then; while taxiing; ground control directed an immediate frequency change to tower who cleared us for an immediate take off. Approaching V1; the tower called for us to abort the take off. The pilot not flying replied 'negative' as we would not have been able to stop on the remaining runway. When airborne; we got visual contact with a B737 apparently on approach to runway 20. We passed well above the traffic with no TCAS alert. While re-calculating the take off data on the taxiway; we neglected to write down our clearance; so we confirmed it with tower during climb out. The lesson here is not to rush or allow ATC to rush you and be especially alert at airports like this with a non radar environment.
Original NASA ASRS Text
Title: Air Carrier departing MHTG continued take off after being advised by ATC to abort; noting their speed prohibited any abort maneuver.
Narrative: On push back; MHTG Ground Control informed us of a runway change from Runway 02 to Runway 20. We were unable due to runway limited take off weight and requested Runway 02 with 5 KTS tailwind. This required several transmissions back and forth with Ground Control while we requested a new flight plan and manually re-calculated take off data for a flaps 20 take off with 5 KTS tailwind. Then; while taxiing; Ground Control directed an immediate frequency change to Tower who cleared us for an immediate take off. Approaching V1; the Tower called for us to abort the take off. The pilot not flying replied 'Negative' as we would not have been able to stop on the remaining runway. When airborne; we got visual contact with a B737 apparently on approach to Runway 20. We passed well above the traffic with no TCAS alert. While re-calculating the take off data on the taxiway; we neglected to write down our clearance; so we confirmed it with Tower during climb out. The lesson here is not to rush or allow ATC to rush you and be especially alert at airports like this with a non radar environment.
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.