37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 647057 |
Time | |
Date | 200502 |
Place | |
Locale Reference | airport : phl.airport |
State Reference | PA |
Altitude | agl single value : 0 |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Controlling Facilities | tower : fai.tower |
Operator | common carrier : air carrier |
Make Model Name | A321 |
Operating Under FAR Part | Part 121 |
Flight Phase | ground : taxi |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | tower : phl.tower |
Operator | common carrier : air carrier |
Make Model Name | A320 |
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 : flight engineer pilot : atp |
Experience | flight time last 90 days : 200 flight time total : 18600 flight time type : 3000 |
ASRS Report | 647057 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Events | |
Anomaly | conflict : ground critical incursion : runway non adherence : required legal separation non adherence : published procedure |
Independent Detector | other flight crewa |
Resolutory Action | flight crew : took evasive action |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Problem Areas | Company Airport ATC Human Performance FAA |
Primary Problem | ATC Human Performance |
Air Traffic Incident | Intra Facility Coordination Failure Operational Error |
Situations | |
ATC Facility | procedure or policy : phl.tower |
Airport | markings : phl.airport |
Narrative:
Landed runway 9R. We were the #2 aircraft holding short of runway 9L at taxiway north. Both aircraft cleared to cross and contact ramp at spot 8. Aircraft ahead stopped short of spot 8; turned left on taxiway K to go to spot 7. This left about half of our aircraft on the runway side of the hold bars with no way to maneuver clear of the runway. Tower on runway 9L cleared a company aircraft to departure. We switched back to the controller; who cleared us across and advised him we were not clear of runway 9L. He acknowledged our transmission; but the company aircraft continued its takeoff. I contacted the tower supervisor on arrival at the gate and followed up with the tower qa manager the next day. The manager reviewed the tapes; asde and amass data and confirmed we were clear of the runway; despite what the markings on the ground showed. This particular location seems to be an accident waiting to happen. I've been in the same situation in the left seat; jumpseat; and in the cabin. We are caught between 2 local controllers; ground; and ramp. This situation needs to be resolved. Callback conversation with reporter revealed the following information: the reporter stated that the local controller handling runway 9R arrivals issued a runway 9L crossing clearance and instructed him to contact ramp control. After crossing runway 9L; the preceding aircraft; also trying to contact ramp control; slowed/stopped; preventing the reporter from clearing runway 9L. The reporter said he went back to the local controller who issued the crossing clearance; advised his aircraft was not clear of runway 9L; but a takeoff clearance was still issued for a runway 9L departure. The reporter stated ATC blames ramp control and ramp control site personnel turnover as problem areas. The reporter also questioned the amass programmed 'clear area' vs the hold lines on the taxiway possibly giving ATC and flight crew's differing concepts as to actual runway clearance.
Original NASA ASRS Text
Title: A321 CAPT EXPRESSED CONCERN REGARDING ATC AND RAMP CTL TAXIING COORDINATION AND QUESTIONED USE OF AMASS DATA AT PHL.
Narrative: LANDED RWY 9R. WE WERE THE #2 ACFT HOLDING SHORT OF RWY 9L AT TXWY N. BOTH ACFT CLRED TO CROSS AND CONTACT RAMP AT SPOT 8. ACFT AHEAD STOPPED SHORT OF SPOT 8; TURNED L ON TXWY K TO GO TO SPOT 7. THIS LEFT ABOUT HALF OF OUR ACFT ON THE RWY SIDE OF THE HOLD BARS WITH NO WAY TO MANEUVER CLR OF THE RWY. TWR ON RWY 9L CLRED A COMPANY ACFT TO DEP. WE SWITCHED BACK TO THE CTLR; WHO CLRED US ACROSS AND ADVISED HIM WE WERE NOT CLR OF RWY 9L. HE ACKNOWLEDGED OUR TRANSMISSION; BUT THE COMPANY ACFT CONTINUED ITS TKOF. I CONTACTED THE TWR SUPERVISOR ON ARR AT THE GATE AND FOLLOWED UP WITH THE TWR QA MANAGER THE NEXT DAY. THE MANAGER REVIEWED THE TAPES; ASDE AND AMASS DATA AND CONFIRMED WE WERE CLR OF THE RWY; DESPITE WHAT THE MARKINGS ON THE GND SHOWED. THIS PARTICULAR LOCATION SEEMS TO BE AN ACCIDENT WAITING TO HAPPEN. I'VE BEEN IN THE SAME SIT IN THE L SEAT; JUMPSEAT; AND IN THE CABIN. WE ARE CAUGHT BETWEEN 2 LOCAL CTLRS; GND; AND RAMP. THIS SIT NEEDS TO BE RESOLVED. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE RPTR STATED THAT THE LOCAL CTLR HANDLING RWY 9R ARRIVALS ISSUED A RWY 9L CROSSING CLRNC AND INSTRUCTED HIM TO CONTACT RAMP CTL. AFTER CROSSING RWY 9L; THE PRECEDING ACFT; ALSO TRYING TO CONTACT RAMP CTL; SLOWED/STOPPED; PREVENTING THE RPTR FROM CLEARING RWY 9L. THE RPTR SAID HE WENT BACK TO THE LOCAL CTLR WHO ISSUED THE CROSSING CLRNC; ADVISED HIS ACFT WAS NOT CLR OF RWY 9L; BUT A TKOF CLRNC WAS STILL ISSUED FOR A RWY 9L DEP. THE RPTR STATED ATC BLAMES RAMP CTL AND RAMP CTL SITE PERSONNEL TURNOVER AS PROB AREAS. THE RPTR ALSO QUESTIONED THE AMASS PROGRAMMED 'CLR AREA' VS THE HOLD LINES ON THE TXWY POSSIBLY GIVING ATC AND FLC'S DIFFERING CONCEPTS AS TO ACTUAL RWY CLRNC.
Data retrieved from NASA's ASRS site as of January 2009 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.