A320 crew had to stop abruptly to avoid a collision with a B737 on takeoff roll on runway 9L in phl.

Attributes
ACN	485164
Time
Date	200008
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	A320
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	B737-300
Operating Under FAR Part	Part 121
Flight Phase	ground : takeoff roll
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer instruction : instructor oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 150 flight time total : 10500 flight time type : 4000
ASRS Report	485164
Person 2
Affiliation	company : air carrier
Function	flight crew : captain instruction : trainee
Qualification	pilot : atp
Events
Anomaly	conflict : ground critical ground encounters other non adherence : far non adherence : published procedure
Independent Detector	other flight crewa
Resolutory Action	flight crew : took evasive action other
Miss Distance	horizontal : 2000 vertical : 0
Supplementary
Problem Areas	Airport Flight Crew Human Performance ATC Human Performance
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Error Intra Facility Coordination Failure

Narrative:

After landing in phl on runway 9R, I was cleared to stay with tower (135.1) and cross runway 9L at taxiway north. I was conducting captain IOE and was PIC/PNF in the right seat. Prior to crossing runway 9L, I noticed aircraft apparently departing full length. I do not believe my crossing clearance included information that an aircraft was holding in position. Upon realizing that the other aircraft (B737-300 or 400) was in fact departing, I applied full wheel brakes to stop short of runway, but past hold line. I do not know whether other aircraft was departing without clearance or was cleared by the tower controller for runway 9L, however, I did notice that landing, taxi, and takeoff lights were off, suggesting possible cockpit confusion. I strongly believe that all movements on any given runway surface should be controled on the same frequency. I had been cleared to cross by phl tower on 135.1, and runway 9L is controled by tower 118.5.

Original NASA ASRS Text

Title: A320 CREW HAD TO STOP ABRUPTLY TO AVOID A COLLISION WITH A B737 ON TKOF ROLL ON RWY 9L IN PHL.

Narrative: AFTER LNDG IN PHL ON RWY 9R, I WAS CLRED TO STAY WITH TWR (135.1) AND CROSS RWY 9L AT TXWY N. I WAS CONDUCTING CAPT IOE AND WAS PIC/PNF IN THE R SEAT. PRIOR TO XING RWY 9L, I NOTICED ACFT APPARENTLY DEPARTING FULL LENGTH. I DO NOT BELIEVE MY XING CLRNC INCLUDED INFO THAT AN ACFT WAS HOLDING IN POS. UPON REALIZING THAT THE OTHER ACFT (B737-300 OR 400) WAS IN FACT DEPARTING, I APPLIED FULL WHEEL BRAKES TO STOP SHORT OF RWY, BUT PAST HOLD LINE. I DO NOT KNOW WHETHER OTHER ACFT WAS DEPARTING WITHOUT CLRNC OR WAS CLRED BY THE TWR CTLR FOR RWY 9L, HOWEVER, I DID NOTICE THAT LNDG, TAXI, AND TKOF LIGHTS WERE OFF, SUGGESTING POSSIBLE COCKPIT CONFUSION. I STRONGLY BELIEVE THAT ALL MOVEMENTS ON ANY GIVEN RWY SURFACE SHOULD BE CTLED ON THE SAME FREQ. I HAD BEEN CLRED TO CROSS BY PHL TWR ON 135.1, AND RWY 9L IS CTLED BY TWR 118.5.

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.