37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 428870 |
Time | |
Date | 199902 |
Day | Thu |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : bos.airport |
State Reference | MA |
Altitude | agl single value : 0 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : bos.tower |
Operator | common carrier : air carrier |
Make Model Name | SF 340A |
Operating Under FAR Part | Part 121 |
Flight Phase | ground : takeoff roll |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | tower : bos.tower |
Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
Flight Phase | descent : approach |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Experience | flight time last 90 days : 100 flight time total : 4050 flight time type : 1100 |
ASRS Report | 728870 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : instrument pilot : commercial pilot : multi engine |
Events | |
Anomaly | conflict : ground less severe other anomaly other |
Independent Detector | other controllera |
Resolutory Action | flight crew : rejected takeoff |
Supplementary | |
Problem Areas | ATC Human Performance |
Primary Problem | ATC Human Performance |
Air Traffic Incident | other |
Narrative:
Departing bos runway 33L at intersection G, we were cleared into position and hold. While rolling onto the runway, we were told by bos tower, 'be ready for immediate takeoff.' after 2 seconds later, 'cleared for takeoff.' while completing the takeoff checklist, we lined up on runway centerline, and as we began moving the power levers forward we were told 'cancel takeoff clearance, turn off at taxiway F.' we taxied/rolled clear at taxiway F. Our next takeoff attempt was successful, however it was almost aborted in the exact same manner due, again, to insufficient spacing between departure and landing traffic. No heads up was given by the tower in either case to 'expect immediate takeoff.' both times cleared 'position and hold,' and almost immediately followed by 'cleared for takeoff.' possible corrective actions: 1) strictly adhere to standard departure intervals/spacing. 2) inform pilot of 'expect immediate takeoff' prior to aircraft entering runway so it can be accepted or declined. 3) open another northwest/southeast runway in boston.
Original NASA ASRS Text
Title: SF34 CREW HAS TKOF CLRNC CANCELED BY BOS TWR DUE TO LNDG TFC.
Narrative: DEPARTING BOS RWY 33L AT INTXN G, WE WERE CLRED INTO POS AND HOLD. WHILE ROLLING ONTO THE RWY, WE WERE TOLD BY BOS TWR, 'BE READY FOR IMMEDIATE TKOF.' AFTER 2 SECONDS LATER, 'CLRED FOR TKOF.' WHILE COMPLETING THE TKOF CHKLIST, WE LINED UP ON RWY CTRLINE, AND AS WE BEGAN MOVING THE PWR LEVERS FORWARD WE WERE TOLD 'CANCEL TKOF CLRNC, TURN OFF AT TXWY F.' WE TAXIED/ROLLED CLR AT TXWY F. OUR NEXT TKOF ATTEMPT WAS SUCCESSFUL, HOWEVER IT WAS ALMOST ABORTED IN THE EXACT SAME MANNER DUE, AGAIN, TO INSUFFICIENT SPACING BTWN DEP AND LNDG TFC. NO HEADS UP WAS GIVEN BY THE TWR IN EITHER CASE TO 'EXPECT IMMEDIATE TKOF.' BOTH TIMES CLRED 'POS AND HOLD,' AND ALMOST IMMEDIATELY FOLLOWED BY 'CLRED FOR TKOF.' POSSIBLE CORRECTIVE ACTIONS: 1) STRICTLY ADHERE TO STANDARD DEP INTERVALS/SPACING. 2) INFORM PLT OF 'EXPECT IMMEDIATE TKOF' PRIOR TO ACFT ENTERING RWY SO IT CAN BE ACCEPTED OR DECLINED. 3) OPEN ANOTHER NW/SE RWY IN BOSTON.
Data retrieved from NASA's ASRS site as of July 2007 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.