Air carrier penetrated adjacent airspace without a handoff.

Attributes
ACN	115323
Time
Date	198906
Day	Wed
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : phl
State Reference	PA
Altitude	msl bound lower : 4000 msl bound upper : 11000
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Controlling Facilities	tracon : phl
Operator	common carrier : air carrier
Make Model Name	Light Transport, High Wing, 2 Turboprop Eng
Flight Phase	cruise other
Route In Use	arrival other
Flight Plan	IFR
Aircraft 2
Operator	common carrier : air carrier
Make Model Name	Large Transport, Low Wing, 3 Turbojet Eng
Flight Phase	descent other
Route In Use	arrival other
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : approach
Qualification	controller : radar
ASRS Report	115323
Person 2
Affiliation	government : military
Function	controller : approach
Qualification	controller : radar
Events
Anomaly	non adherence : published procedure other anomaly other
Independent Detector	other controllera
Resolutory Action	other
Consequence	Other
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Inter Facility Coordination Failure Operational Deviation

Narrative:

While working the woodstown sector at phl approach, mcguire approach called to ask for a non-standard routing for air carrier X commuter aircraft. They wanted to put the aircraft on the runway 27R localizer instead of V312 to DDD VOR. I approved the frequently used non standard routing for the aircraft. I proceeded to get very busy and due to short staffing we had combined sectors up. I was also working/sharing the final vector airspace. It means I was coordinating every arrival with another controller for a sequence. I had a few arrs and so did the other controller. We coordinated a sequence and I suddenly noticed a splat (an aircraft with a beacon west/O mode C) about 15 mi east of phl and it then suddenly showed an altitude of 11000'. The other controller had an large transport heading right for this target descending from 5000 to 3000'. I checked the beacon code out and called mcguire approach and sure enough it was air carrier X I had approved earlier. They made no handoff on the aircraft and were totally at fault by entering my airspace west/O a handoff. The conflict was resolved by immediate action by myself to notify both controllers of the very potential midair collision. If the computer would have put an a/north tag on the splat like it should have, the situation would have never gotten that far. Just another example of the FAA's antiquated equipment.

Original NASA ASRS Text

Title: ACR PENETRATED ADJACENT AIRSPACE WITHOUT A HANDOFF.

Narrative: WHILE WORKING THE WOODSTOWN SECTOR AT PHL APCH, MCGUIRE APCH CALLED TO ASK FOR A NON-STANDARD ROUTING FOR ACR X COMMUTER ACFT. THEY WANTED TO PUT THE ACFT ON THE RWY 27R LOC INSTEAD OF V312 TO DDD VOR. I APPROVED THE FREQUENTLY USED NON STANDARD ROUTING FOR THE ACFT. I PROCEEDED TO GET VERY BUSY AND DUE TO SHORT STAFFING WE HAD COMBINED SECTORS UP. I WAS ALSO WORKING/SHARING THE FINAL VECTOR AIRSPACE. IT MEANS I WAS COORDINATING EVERY ARR WITH ANOTHER CTLR FOR A SEQUENCE. I HAD A FEW ARRS AND SO DID THE OTHER CTLR. WE COORDINATED A SEQUENCE AND I SUDDENLY NOTICED A SPLAT (AN ACFT WITH A BEACON W/O MODE C) ABOUT 15 MI E OF PHL AND IT THEN SUDDENLY SHOWED AN ALT OF 11000'. THE OTHER CTLR HAD AN LGT HDG RIGHT FOR THIS TARGET DSNDING FROM 5000 TO 3000'. I CHKED THE BEACON CODE OUT AND CALLED MCGUIRE APCH AND SURE ENOUGH IT WAS ACR X I HAD APPROVED EARLIER. THEY MADE NO HDOF ON THE ACFT AND WERE TOTALLY AT FAULT BY ENTERING MY AIRSPACE W/O A HDOF. THE CONFLICT WAS RESOLVED BY IMMEDIATE ACTION BY MYSELF TO NOTIFY BOTH CTLRS OF THE VERY POTENTIAL MIDAIR COLLISION. IF THE COMPUTER WOULD HAVE PUT AN A/N TAG ON THE SPLAT LIKE IT SHOULD HAVE, THE SITUATION WOULD HAVE NEVER GOTTEN THAT FAR. JUST ANOTHER EXAMPLE OF THE FAA'S ANTIQUATED EQUIP.

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