Phl local controller voiced concern regarding a supervisor directed event involving a king air makin...

Narrative:

King air was inbound for runway 17 on a recorded run. A B737-300 was inbound to runway 27R. I advised the front line manager (supervisor) when both aircraft were 6 miles out that there was a potential conflict at the airport. He told me that there was no problem with the B737 passing through the intersection while the king air was on the recorded run. I was aware that passing through the intersection did not disturb the recorded run; but I felt that there might still be a tie at the intersection. He ordered me to assign the B737 runway 27L; which does not intersect with runway 17. I tried to raise objection to this action; because I was still concerned that there might be a potential conflict because the king air was low approach only; and his departure course could still put him in the vicinity of the B737. He became very frustrated with me questioning his authority; and again ordered me to assign the B737 runway 27L. I pointed the B737 out to the king air when it was on about a 3 mile final. At that time he advised the traffic in sight and said he would maintain visual separation from it. I also had both aircraft in sight. The king air did pass above and behind the B737. I was very uncomfortable with the front line manager ordering me to run such a tight and potentially dangerous operation.

Original NASA ASRS Text

Title: PHL Local Controller voiced concern regarding a Supervisor directed event involving a King Air making a low approach to Runway 17 and an arrival to Runway 27L; alleging situation was potentially unsafe.

Narrative: King Air was inbound for Runway 17 on a recorded run. A B737-300 was inbound to Runway 27R. I advised the Front Line Manager (Supervisor) when both aircraft were 6 miles out that there was a potential conflict at the airport. He told me that there was no problem with the B737 passing through the intersection while the King Air was on the recorded run. I was aware that passing through the intersection did not disturb the recorded run; but I felt that there might still be a tie at the intersection. He ordered me to assign the B737 Runway 27L; which does not intersect with Runway 17. I tried to raise objection to this action; because I was still concerned that there might be a potential conflict because the King Air was low approach only; and his departure course could still put him in the vicinity of the B737. He became very frustrated with me questioning his authority; and again ordered me to assign the B737 Runway 27L. I pointed the B737 out to the King Air when it was on about a 3 mile final. At that time he advised the traffic in sight and said he would maintain visual separation from it. I also had both aircraft in sight. The King Air did pass above and behind the B737. I was very uncomfortable with the Front Line Manager ordering me to run such a tight and potentially dangerous operation.

Data retrieved from NASA's ASRS site as of April 2012 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.

Attributes
ACN	822915
Time
Date	200902
Local Time Of Day	0601-1200
Place
Locale Reference	PHL.Airport
State Reference	PA
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	Beechcraft Twin Turboprop or Jet Undifferentiated or Other Model
Operating Under FAR Part	Part 91
Flight Phase	Landing
Flight Plan	VFR
Aircraft 2
Make Model Name	B737 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	Initial Approach
Route In Use	Visual Approach
Flight Plan	IFR
Person 1
Function	Local
Experience	Air Traffic Control Radar 8 Air Traffic Control Time Certified In Pos 1 (yrs) 2
Events
Anomaly	Conflict Airborne Conflict

Phl local controller voiced concern regarding a supervisor directed event involving a king air making a low approach to runway 17 and an arrival to runway 27L; alleging situation was potentially unsafe.