Phl local controller experienced loss of separation between landing and departing traffic on interse...

Attributes
ACN	582739
Time
Date	200305
Day	Fri
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : phl.airport
State Reference	PA
Altitude	agl single value : 0
Environment
Flight Conditions	Marginal
Light	Daylight
Aircraft 1
Controlling Facilities	tower : phl.tower
Operator	common carrier : air carrier
Make Model Name	A320
Operating Under FAR Part	Part 121
Flight Phase	ground : takeoff roll
Flight Plan	IFR
Aircraft 2
Controlling Facilities	tower : phl.tower
Operator	general aviation : corporate
Make Model Name	Learjet 25
Operating Under FAR Part	Part 91
Flight Phase	descent : approach landing : roll
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : local
Qualification	controller : radar
Experience	controller non radar : 3 controller radar : 10 controller time certified in position1 : 8
ASRS Report	582739
Person 2
Affiliation	government : faa
Function	controller : supervisor
Events
Anomaly	conflict : ground less severe non adherence : required legal separation non adherence : published procedure
Independent Detector	other controllera
Resolutory Action	none taken : anomaly accepted
Consequence	faa : investigated
Miss Distance	horizontal : 4000
Supplementary
Problem Areas	ATC Human Performance
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Error

Narrative:

I cleared air carrier X, A320, for immediate takeoff on runway 9L using anticipated separation. LJ25 was cleared to land on runway 17 (intersecting). By the time air carrier X rolled, I realized standard separation would not exist when learjet crossed landing threshold for runway 17. I then asked the supervisor if I should send LJ25 around. The supervisor did not respond to me. I then realized it would be safer for LJ25 to land rather than go around and create a possible airborne conflict with air carrier X who was taking off. LJ25 landed safely and did not come closer than 5000 ft to air carrier X before air carrier X rotated. It was a 'technical' loss of runway separation but a very controled one. The biggest problem was that the supervisor 'froze' when he was asked for assistance.

Original NASA ASRS Text

Title: PHL LCL CTLR EXPERIENCED LOSS OF SEPARATION BTWN LNDG AND DEPARTING TFC ON INTERSECTING RWYS.

Narrative: I CLRED ACR X, A320, FOR IMMEDIATE TKOF ON RWY 9L USING ANTICIPATED SEPARATION. LJ25 WAS CLRED TO LAND ON RWY 17 (INTERSECTING). BY THE TIME ACR X ROLLED, I REALIZED STANDARD SEPARATION WOULD NOT EXIST WHEN LEARJET CROSSED LNDG THRESHOLD FOR RWY 17. I THEN ASKED THE SUPVR IF I SHOULD SEND LJ25 AROUND. THE SUPVR DID NOT RESPOND TO ME. I THEN REALIZED IT WOULD BE SAFER FOR LJ25 TO LAND RATHER THAN GO AROUND AND CREATE A POSSIBLE AIRBORNE CONFLICT WITH ACR X WHO WAS TAKING OFF. LJ25 LANDED SAFELY AND DID NOT COME CLOSER THAN 5000 FT TO ACR X BEFORE ACR X ROTATED. IT WAS A 'TECHNICAL' LOSS OF RWY SEPARATION BUT A VERY CTLED ONE. THE BIGGEST PROB WAS THAT THE SUPVR 'FROZE' WHEN HE WAS ASKED FOR ASSISTANCE.

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.

Phl local controller experienced loss of separation between landing and departing traffic on intersecting runways.