Air carrier Y takeoff on occupied runway had less than standard separation from air carrier Y. Syste...

Attributes
ACN	250952
Time
Date	199309
Day	Wed
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : phl
State Reference	PA
Altitude	agl bound lower : 0 agl bound upper : 200
Environment
Flight Conditions	VMC
Light	Dusk
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	Light Transport, High Wing, 2 Turboprop Eng
Flight Phase	ground other : taxi
Flight Plan	IFR
Aircraft 2
Operator	common carrier : air carrier
Make Model Name	Light Transport, High Wing, 2 Turboprop Eng
Flight Phase	climbout : initial climbout : takeoff
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 240 flight time total : 5500 flight time type : 3000
ASRS Report	250952
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : commercial pilot : instrument
Events
Anomaly	conflict : nmac non adherence : published procedure non adherence : required legal separation
Independent Detector	other flight crewa
Resolutory Action	none taken : insufficient time
Consequence	faa : investigated
Miss Distance	horizontal : 0 vertical : 200
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Error Inter Facility Coordination Failure

Narrative:

Air carrier X holding short of runway 9L at phl. An medium large transport just lifted off. Ground control then gave air carrier X clearance to cross runway 9L at taxiway U. As I began to cross the runway, I saw what appeared to be a company light transport in position on the runway with his 'line-up' checks completed, i.e., landing lights on. We were in the middle of that runway when that light transport lifted off. Normal phl operations use of ground control to cross active runways (9L/27R) when taxiing for runways 35 and 27L, poses the problem of not hearing the takeoff clearance of the other aircraft. However, when landing on runway 27L or 9R the tower controller instructs you when to cross runway 9L/27R and passes you off to the ground controller after clearing the active runway. Also, company procedures call for the 'line-up' checks to be completed any time you take the active runway. The landing lights are on regardless if the clearance was position and hold, or a takeoff clearance, which led me to believe that aircraft was position and hold.

Original NASA ASRS Text

Title: ACR Y TKOF ON OCCUPIED RWY HAD LTSS FROM ACR Y. SYS ERROR.

Narrative: ACR X HOLDING SHORT OF RWY 9L AT PHL. AN MLG JUST LIFTED OFF. GND CTL THEN GAVE ACR X CLRNC TO CROSS RWY 9L AT TXWY U. AS I BEGAN TO CROSS THE RWY, I SAW WHAT APPEARED TO BE A COMPANY LTT IN POS ON THE RWY WITH HIS 'LINE-UP' CHKS COMPLETED, I.E., LNDG LIGHTS ON. WE WERE IN THE MIDDLE OF THAT RWY WHEN THAT LTT LIFTED OFF. NORMAL PHL OPS USE OF GND CTL TO CROSS ACTIVE RWYS (9L/27R) WHEN TAXIING FOR RWYS 35 AND 27L, POSES THE PROB OF NOT HEARING THE TKOF CLRNC OF THE OTHER ACFT. HOWEVER, WHEN LNDG ON RWY 27L OR 9R THE TWR CTLR INSTRUCTS YOU WHEN TO CROSS RWY 9L/27R AND PASSES YOU OFF TO THE GND CTLR AFTER CLRING THE ACTIVE RWY. ALSO, COMPANY PROCS CALL FOR THE 'LINE-UP' CHKS TO BE COMPLETED ANY TIME YOU TAKE THE ACTIVE RWY. THE LNDG LIGHTS ARE ON REGARDLESS IF THE CLRNC WAS POS AND HOLD, OR A TKOF CLRNC, WHICH LED ME TO BELIEVE THAT ACFT WAS POS AND HOLD.

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.

Air carrier Y takeoff on occupied runway had less than standard separation from air carrier Y. System error.