 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Multiple runway operation intersecting runways air carrier X aborted takeoff air carrier Y made go around to avoid conflict at intersection of runways.
| Attributes | |
| ACN | 211747 |
| Time | |
| Date | 199206 |
| Day | Tue |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | airport : phl |
| State Reference | PA |
| Altitude | agl bound lower : 0 agl bound upper : 0 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tower : phl |
| Operator | common carrier : air carrier |
| Make Model Name | Light Transport, High Wing, 2 Turboprop Eng |
| Flight Phase | climbout : takeoff other |
| Flight Plan | IFR |
| Aircraft 2 | |
| Operator | common carrier : air carrier |
| Make Model Name | Medium Large Transport, Low Wing, 2 Turbojet Eng |
| Flight Phase | descent : approach landing : go around |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : commercial pilot : instrument pilot : cfi |
| Experience | flight time last 90 days : 240 flight time total : 3600 flight time type : 1900 |
| ASRS Report | 211747 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp |
| Events | |
| Anomaly | conflict : ground less severe conflict : airborne less severe non adherence : clearance |
| Independent Detector | other controllera other flight crewa |
| Resolutory Action | controller : issued new clearance flight crew : rejected takeoff other |
| Consequence | Other |
| Miss Distance | horizontal : 2000 vertical : 200 |
| Supplementary | |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | other |
Narrative:
I was PNF, cleared for takeoff on runway 17. Advised in clearance that traffic was '2 out for runway 27R.' that signaled me to keep a look out. That is not an unusually close distance. I believe I have taken off in the past in similar situations with no conflict. Also from the takeoff position on runway 17, you cannot see aircraft approaching to land on runway 27R for the first approximately 500-1000 ft due to a hangar blocking your sight. The captain set torque, I fine-tuned the setting. As I set power and scanned the instruments (which takes concentration in our aircraft due to the throttles being very sensitive, and the engines often creep on the power setting), I looked up and saw the aircraft for runway 27R. I immediately sensed a conflict and advised the captain. I advised the captain again, I believe, that it didn't look good. He acknowledged and continued the takeoff. ATC then said something to us, I believe it was air carrier X, no delay through the intersection. I acknowledged, I believe, with 'no delay air carrier X.' it was tough to understand what she said, because me and the captain were discussing the situation, when she interrupted. Just when the captain was deciding to abort, ATC advised 'air carrier X, cancel takeoff clearance.' I acknowledged. Tower then advised air carrier Y on final to go around. She asked us to hold short. I acknowledged we could and would hold short. I believe the hangar's blocking our view at the beginning of the runway were a factor. If I had seen the aircraft before acknowledging the takeoff clearance, I would have advised the captain and strongly urged we wait until the aircraft passes. I think there is a mindset though, of I started the takeoff, I am going to takeoff. If you abort, and it really wasn't a valid reason, that you will get in trouble, or, you only abort for engine failure or fire.
Original NASA ASRS Text
Title: MULTIPLE RWY OP INTERSECTING RWYS ACR X ABORTED TKOF ACR Y MADE GAR TO AVOID CONFLICT AT INTXN OF RWYS.
Narrative: I WAS PNF, CLRED FOR TKOF ON RWY 17. ADVISED IN CLRNC THAT TFC WAS '2 OUT FOR RWY 27R.' THAT SIGNALED ME TO KEEP A LOOK OUT. THAT IS NOT AN UNUSUALLY CLOSE DISTANCE. I BELIEVE I HAVE TAKEN OFF IN THE PAST IN SIMILAR SITUATIONS WITH NO CONFLICT. ALSO FROM THE TKOF POS ON RWY 17, YOU CANNOT SEE ACFT APCHING TO LAND ON RWY 27R FOR THE FIRST APPROX 500-1000 FT DUE TO A HANGAR BLOCKING YOUR SIGHT. THE CAPT SET TORQUE, I FINE-TUNED THE SETTING. AS I SET PWR AND SCANNED THE INSTS (WHICH TAKES CONCENTRATION IN OUR ACFT DUE TO THE THROTTLES BEING VERY SENSITIVE, AND THE ENGS OFTEN CREEP ON THE PWR SETTING), I LOOKED UP AND SAW THE ACFT FOR RWY 27R. I IMMEDIATELY SENSED A CONFLICT AND ADVISED THE CAPT. I ADVISED THE CAPT AGAIN, I BELIEVE, THAT IT DIDN'T LOOK GOOD. HE ACKNOWLEDGED AND CONTINUED THE TKOF. ATC THEN SAID SOMETHING TO US, I BELIEVE IT WAS ACR X, NO DELAY THROUGH THE INTXN. I ACKNOWLEDGED, I BELIEVE, WITH 'NO DELAY ACR X.' IT WAS TOUGH TO UNDERSTAND WHAT SHE SAID, BECAUSE ME AND THE CAPT WERE DISCUSSING THE SITUATION, WHEN SHE INTERRUPTED. JUST WHEN THE CAPT WAS DECIDING TO ABORT, ATC ADVISED 'ACR X, CANCEL TKOF CLRNC.' I ACKNOWLEDGED. TWR THEN ADVISED ACR Y ON FINAL TO GAR. SHE ASKED US TO HOLD SHORT. I ACKNOWLEDGED WE COULD AND WOULD HOLD SHORT. I BELIEVE THE HANGAR'S BLOCKING OUR VIEW AT THE BEGINNING OF THE RWY WERE A FACTOR. IF I HAD SEEN THE ACFT BEFORE ACKNOWLEDGING THE TKOF CLRNC, I WOULD HAVE ADVISED THE CAPT AND STRONGLY URGED WE WAIT UNTIL THE ACFT PASSES. I THINK THERE IS A MINDSET THOUGH, OF I STARTED THE TKOF, I AM GOING TO TKOF. IF YOU ABORT, AND IT REALLY WASN'T A VALID REASON, THAT YOU WILL GET IN TROUBLE, OR, YOU ONLY ABORT FOR ENG FAILURE OR FIRE.
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.