Flight of two fgt entered adjacent facility's airspace without proper coordination.

Attributes
ACN	169287
Time
Date	199102
Day	Fri
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : hcm airport : ric airport : orf
State Reference	VA
Altitude	msl bound lower : 3000 msl bound upper : 3000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : ric tracon : orf tower : ric
Operator	other
Make Model Name	Fighter
Flight Phase	cruise other
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : departure
Qualification	controller : non radar
ASRS Report	169287
Person 2
Affiliation	government : faa
Function	controller : local
Qualification	controller : non radar
Events
Anomaly	non adherence : published procedure other anomaly other
Independent Detector	other controllera other flight crewa
Resolutory Action	flight crew : became reoriented other
Consequence	Other
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Deviation

Narrative:

I was working east feeder. Tower had a flight of 2/fgt for departure. The aircraft departed but never established radio contact prior to departure. The local controller never ensured I was aware that the flight departed, nor was I aware the data tag didn't acquire when the flight departed. The flight called another controller and asked for assistance. This controller in turn asked the local controller who 2/fgt was. At this time I heard her conversation and said I was suppose to have the 2/fgt flight. She changed them to my frequency but they were unable to establish radio contact. Finally they did call me on VHF 126.4. I asked, were they on the ground for takeoff roll. They advised neg, they were airborne over orf. I immediately issued the transponder code they were assigned; coordination with the orf controller that the aircraft were 5 southwest of the hcm VOR at 3000'. She idented the aircraft and called them radar. I tagged the aircraft manually, then had radar data forced tag and strip through the computer and with interface handed off the flight to orf approach. I feel this would have never happened had the local controller at richmond tower been more aware of where his departure traffic was and once the aircraft didn't tag if he would have coordination with the radar controller. The failure of the computer system to tag the aircraft on departure is secondary!

Original NASA ASRS Text

Title: FLT OF TWO FGT ENTERED ADJACENT FAC'S AIRSPACE WITHOUT PROPER COORD.

Narrative: I WAS WORKING E FEEDER. TWR HAD A FLT OF 2/FGT FOR DEP. THE ACFT DEPARTED BUT NEVER ESTABLISHED RADIO CONTACT PRIOR TO DEP. THE LCL CTLR NEVER ENSURED I WAS AWARE THAT THE FLT DEPARTED, NOR WAS I AWARE THE DATA TAG DIDN'T ACQUIRE WHEN THE FLT DEPARTED. THE FLT CALLED ANOTHER CTLR AND ASKED FOR ASSISTANCE. THIS CTLR IN TURN ASKED THE LCL CTLR WHO 2/FGT WAS. AT THIS TIME I HEARD HER CONVERSATION AND SAID I WAS SUPPOSE TO HAVE THE 2/FGT FLT. SHE CHANGED THEM TO MY FREQ BUT THEY WERE UNABLE TO ESTABLISH RADIO CONTACT. FINALLY THEY DID CALL ME ON VHF 126.4. I ASKED, WERE THEY ON THE GND FOR TKOF ROLL. THEY ADVISED NEG, THEY WERE AIRBORNE OVER ORF. I IMMEDIATELY ISSUED THE XPONDER CODE THEY WERE ASSIGNED; COORD WITH THE ORF CTLR THAT THE ACFT WERE 5 SW OF THE HCM VOR AT 3000'. SHE IDENTED THE ACFT AND CALLED THEM RADAR. I TAGGED THE ACFT MANUALLY, THEN HAD RADAR DATA FORCED TAG AND STRIP THROUGH THE COMPUTER AND WITH INTERFACE HANDED OFF THE FLT TO ORF APCH. I FEEL THIS WOULD HAVE NEVER HAPPENED HAD THE LCL CTLR AT RICHMOND TWR BEEN MORE AWARE OF WHERE HIS DEP TFC WAS AND ONCE THE ACFT DIDN'T TAG IF HE WOULD HAVE COORD WITH THE RADAR CTLR. THE FAILURE OF THE COMPUTER SYS TO TAG THE ACFT ON DEP IS SECONDARY!

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.