37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 324513 |
Time | |
Date | 199512 |
Day | Wed |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : clt |
State Reference | NC |
Altitude | agl bound lower : 0 agl bound upper : 0 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | B737-300 |
Operating Under FAR Part | Part 121 |
Navigation In Use | Other Other |
Flight Phase | climbout : takeoff |
Flight Plan | IFR |
Aircraft 2 | |
Operator | common carrier : air carrier |
Make Model Name | B737-300 |
Operating Under FAR Part | Part 121 |
Navigation In Use | Other Other |
Flight Phase | ground other : taxi |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : flight engineer pilot : atp |
Experience | controller non radar : 2 flight time last 90 days : 200 flight time total : 17000 flight time type : 1000 |
ASRS Report | 324513 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : atp |
Experience | flight time last 90 days : 175 flight time total : 9000 flight time type : 5000 |
ASRS Report | 324520 |
Events | |
Anomaly | conflict : ground less severe non adherence : required legal separation |
Independent Detector | other controllera |
Resolutory Action | controller : issued new clearance none taken : detected after the fact |
Consequence | faa : reviewed incident with flight crew |
Miss Distance | horizontal : 100 vertical : 0 |
Supplementary | |
Primary Problem | ATC Human Performance |
Air Traffic Incident | Operational Error |
Narrative:
Full aircraft, 116800 pounds takeoff gross weight, 1 acm (jump seater) in cockpit, in the communications loop (speakers on, acm qualified on aircraft type). Cleared for takeoff, as aircraft which landed runway 36R cleared intersection of runways 5 and 36R. With full power set and speed approximately 30 KTS, I noted and pointed out to crew a B737 entering taxiway right, apparently taxiing to runway 36R. I noted that his speed made it appear he may be intending to cross our takeoff runway (runway 5). As I pointed out this possible conflict to the crew, the aircraft on taxiway right came to a stop short of the runway 5 edge. My speed at this point 60- 80 KTS. As we passed 110 KTS, clt local controller transmitted what sounded like 'air carrier X, negative,' a pause and then 'air carrier X, takeoff clearance canceled.' I was, at this point, a few KTS below my V1 speed, and judged that an abort would carry me through the intersection with taxiway right and that the risks of a high-speed abort far outweighed any likely benefit. I instructed the first officer to tell tower 'negative, too late.' takeoff and flight were uneventful. We observed the aircraft at taxiway right to be stopped well short of runway edge, and aircraft holding in position for takeoff on runway 36R. Tower asked us to call, after landing pbi. On phone, supervisor stated that ground controller had indeed cleared other aircraft to cross runway 5. Apparently, crew of other aircraft saw my lights come on as we initiated takeoff roll, and stopped on their own. Controllers realized error and issued instructions to both aircraft as an attempt to prevent collision. Factors: all exterior lights on when cleared for takeoff, crew members clearing left and right before entering a runway, even when positively cleared to cross it. Possible compounding of a bad situation by issuing clearance cancellation to aircraft traveling 130 mph. Under conditions of restr visibility, this would have been a collision involving over 200 passenger.
Original NASA ASRS Text
Title: CTLR CLRS AN ACR ACFT FOR TKOF WHILE ANOTHER ACFT TAXIING IS CLRED ACROSS THE RWY. CTLR ATTEMPTS TO ABORT THE DEP ACR, BUT SPD DOES NOT ALLOW AN ABORT. TAXIING ACFT HELD SHORT OF RWY, BUT NOT THE HOLD LINE.
Narrative: FULL ACFT, 116800 LBS TKOF GROSS WT, 1 ACM (JUMP SEATER) IN COCKPIT, IN THE COMS LOOP (SPEAKERS ON, ACM QUALIFIED ON ACFT TYPE). CLRED FOR TKOF, AS ACFT WHICH LANDED RWY 36R CLRED INTXN OF RWYS 5 AND 36R. WITH FULL PWR SET AND SPEED APPROX 30 KTS, I NOTED AND POINTED OUT TO CREW A B737 ENTERING TXWY R, APPARENTLY TAXIING TO RWY 36R. I NOTED THAT HIS SPD MADE IT APPEAR HE MAY BE INTENDING TO CROSS OUR TKOF RWY (RWY 5). AS I POINTED OUT THIS POSSIBLE CONFLICT TO THE CREW, THE ACFT ON TXWY R CAME TO A STOP SHORT OF THE RWY 5 EDGE. MY SPD AT THIS POINT 60- 80 KTS. AS WE PASSED 110 KTS, CLT LCL CTLR XMITTED WHAT SOUNDED LIKE 'ACR X, NEGATIVE,' A PAUSE AND THEN 'ACR X, TKOF CLRNC CANCELED.' I WAS, AT THIS POINT, A FEW KTS BELOW MY V1 SPD, AND JUDGED THAT AN ABORT WOULD CARRY ME THROUGH THE INTXN WITH TXWY R AND THAT THE RISKS OF A HIGH-SPD ABORT FAR OUTWEIGHED ANY LIKELY BENEFIT. I INSTRUCTED THE FO TO TELL TWR 'NEGATIVE, TOO LATE.' TKOF AND FLT WERE UNEVENTFUL. WE OBSERVED THE ACFT AT TXWY R TO BE STOPPED WELL SHORT OF RWY EDGE, AND ACFT HOLDING IN POS FOR TKOF ON RWY 36R. TWR ASKED US TO CALL, AFTER LNDG PBI. ON PHONE, SUPVR STATED THAT GND CTLR HAD INDEED CLRED OTHER ACFT TO CROSS RWY 5. APPARENTLY, CREW OF OTHER ACFT SAW MY LIGHTS COME ON AS WE INITIATED TKOF ROLL, AND STOPPED ON THEIR OWN. CTLRS REALIZED ERROR AND ISSUED INSTRUCTIONS TO BOTH ACFT AS AN ATTEMPT TO PREVENT COLLISION. FACTORS: ALL EXTERIOR LIGHTS ON WHEN CLRED FOR TKOF, CREW MEMBERS CLRING L AND R BEFORE ENTERING A RWY, EVEN WHEN POSITIVELY CLRED TO CROSS IT. POSSIBLE COMPOUNDING OF A BAD SIT BY ISSUING CLRNC CANCELLATION TO ACFT TRAVELING 130 MPH. UNDER CONDITIONS OF RESTR VISIBILITY, THIS WOULD HAVE BEEN A COLLISION INVOLVING OVER 200 PAX.
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.