 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A B737-300 flight crew has to abort their takeoff when the PIC notes a B727 taxiing across their runway midfield on frequency with ground control at phl, PA.
| Attributes | |
| ACN | 476276 |
| Time | |
| Date | 200006 |
| Day | Mon |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | airport : phl.airport |
| State Reference | PA |
| Altitude | agl single value : 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 |
| Flight Phase | ground : takeoff roll |
| Flight Plan | IFR |
| Aircraft 2 | |
| Controlling Facilities | tower : phl.tower |
| Operator | common carrier : air carrier |
| Make Model Name | B727-200 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | ground : taxi |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp |
| Experience | flight time last 90 days : 2000 flight time total : 14000 flight time type : 2000 |
| ASRS Report | 476276 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : atp pilot : flight engineer |
| Experience | flight time last 90 days : 150 flight time total : 3500 flight time type : 500 |
| ASRS Report | 475828 |
| Events | |
| Anomaly | conflict : ground less severe non adherence : published procedure non adherence : required legal separation other anomaly other |
| Independent Detector | other flight crewa |
| Resolutory Action | flight crew : rejected takeoff |
| Consequence | faa : reviewed incident with flight crew |
| Miss Distance | horizontal : 2500 vertical : 0 |
| Supplementary | |
| Problem Areas | Airport Flight Crew Human Performance Weather ATC Human Performance |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | Operational Error |
Narrative:
After an ATC delay, a runway change and a rerte, we were finally cleared for takeoff on runway 9L. The first officer went back to make the PA as I pulled onto the runway. When he returned, he took over the aircraft as it was his leg. I confirmed with him that we were cleared to go and he brought the throttles up to 45% N2, then to upright (about 75%) and we started to roll. At that time I looked down the runway and saw a B727 approach the runway from the left about 2000 ft down. Since he seemed to be going a bit fast, I said to the first officer 'hold it.' in other words, don't move the throttles to toga thrust. At this point, the B727 continued across our runway and I aborted the takeoff after about 1000 ft roll total. I asked tower if we had been cleared for takeoff, to which he replied 'yes, cleared for takeoff.' I told him about the other aircraft and that we now had to return to the beginning of the runway for takeoff. I think there was a lack of coordination between local and ground rather than an incursion by the B727, due to the fact that they had just changed from a west operation to an east. 'Cleared for takeoff' doesn't mean the takeoff is clear! Take a look. Supplemental information from acn 475828: good job to my captain scanning entire runway. I will be more vigilant in that respect.
Original NASA ASRS Text
Title: A B737-300 FLC HAS TO ABORT THEIR TKOF WHEN THE PIC NOTES A B727 TAXIING ACROSS THEIR RWY MIDFIELD ON FREQ WITH GND CTL AT PHL, PA.
Narrative: AFTER AN ATC DELAY, A RWY CHANGE AND A RERTE, WE WERE FINALLY CLRED FOR TKOF ON RWY 9L. THE FO WENT BACK TO MAKE THE PA AS I PULLED ONTO THE RWY. WHEN HE RETURNED, HE TOOK OVER THE ACFT AS IT WAS HIS LEG. I CONFIRMED WITH HIM THAT WE WERE CLRED TO GO AND HE BROUGHT THE THROTTLES UP TO 45% N2, THEN TO UPRIGHT (ABOUT 75%) AND WE STARTED TO ROLL. AT THAT TIME I LOOKED DOWN THE RWY AND SAW A B727 APCH THE RWY FROM THE L ABOUT 2000 FT DOWN. SINCE HE SEEMED TO BE GOING A BIT FAST, I SAID TO THE FO 'HOLD IT.' IN OTHER WORDS, DON'T MOVE THE THROTTLES TO TOGA THRUST. AT THIS POINT, THE B727 CONTINUED ACROSS OUR RWY AND I ABORTED THE TKOF AFTER ABOUT 1000 FT ROLL TOTAL. I ASKED TWR IF WE HAD BEEN CLRED FOR TKOF, TO WHICH HE REPLIED 'YES, CLRED FOR TKOF.' I TOLD HIM ABOUT THE OTHER ACFT AND THAT WE NOW HAD TO RETURN TO THE BEGINNING OF THE RWY FOR TKOF. I THINK THERE WAS A LACK OF COORD BTWN LCL AND GND RATHER THAN AN INCURSION BY THE B727, DUE TO THE FACT THAT THEY HAD JUST CHANGED FROM A W OP TO AN E. 'CLRED FOR TKOF' DOESN'T MEAN THE TKOF IS CLR! TAKE A LOOK. SUPPLEMENTAL INFO FROM ACN 475828: GOOD JOB TO MY CAPT SCANNING ENTIRE RWY. I WILL BE MORE VIGILANT IN THAT RESPECT.
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.