Less than standard separation between military fighter and military spacecraft. Operational error.

Date: 1988-12 · Aircraft: Fighter

Anomalies: ATC issue all typesConflict airborne conflict

Synopsis

Less than standard separation between military fighter and military spacecraft. Operational error.

Narrative

Rewritten in plain English from NASA’s original all-caps telegraphic report — facts, figures, and terminology preserved.

Fighter X, being sequenced to the local LFI military base, was given a second heading for intrail restrictions. Spacecraft Y departed for the warning areas requesting 4000 feet. Fighter X was descended to 4000 feet, turned westbound, and spacecraft Y was given direct to the warning areas (eastbound).

Traffic was busy and coordinated by landlines and with ORF flight data people, which caused attention to be taken away from the radar scope. Traffic was given to spacecraft Y about the oncoming fighter, whom I believed I had only descending to 5000 feet (not 4000 feet). Fighter X was advised to maintain 5000 feet; he then advised me radar contact with the opposing direction spacecraft Y, but less than minimum separation had existed.

Callback conversation with reporter revealed the following: reporter gave airports involved and approximate location of conflict. After fighter X reported radar contact on spacecraft Y, the controller climbed fighter X back up to 5000 feet. Lowest fighter got was 4300 feet with spacecraft Y at 4000 feet. Fighter X passed behind spacecraft Y with visual contact. No other corrective action by ATC.

Supplemental info from ACN 99191: I was giving an evaluation on a radar position. I was current but not that proficient. I missed the descent given to the fighter pilot which was okay until trainee turned aircraft towards each other.

Show the original NASA report (verbatim, telegraphic)

FGT X; BEING SEQUENCED TO THE LCL LFI MIL BASE WAS GIVEN A SEBND HDG FOR INTRAIL RESTRICTIONS. SPC Y DEPARTED FOR THE WARNING AREAS REQUESTING 4000'. FGT X WAS DSNDED TO 4000'; TURNED WBOUND AND SPC Y WAS GIVEN DIRECT TO THE WARNING AREAS (EBND). TFC WAS BUSY AND COORD BY LANDLINES AND WITH ORF FLT DATA PEOPLE CAUSED ATTN TO BE TAKEN AWAY FROM THE RADAR SCOPE. TFC WAS GIVEN TO SPC Y ABOUT THE ONCOMING FGT WHO I BELIEVED I HAD ONLY DSNDING TO 5000' (NOT 4000'). FGT X WAS ADVISED TO MAINTAIN 5000'; HE THEN ADVISED ME RADAR CONTACT WITH THE OPP DIRECTION SPC Y; BUT LESS THAN MINIMUM SEP HAD EXISTED. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING: RPTR GAVE ARPTS INVOLVED AND APPROX LOCATION OF CONFLICT. AFTER FGT X RPTED RADAR CONTACT ON SPC Y THE CTLR CLBED FGT X BACK UP TO 5000'. LOWEST FGT GOT WAS 4300' WITH SPC Y AT 4000'. FLT X PASSED BEHIND SPC Y WITH VISUAL CONTACT. NO OTHER CORRECTIVE ACTION BY ATC. SUPPLEMENTAL INFO FROM ACN 99191: I WAS GIVING AN EVALUATION ON A RADAR POS. I WAS CURRENT BUT NOT THAT PROFICIENT. I MISSED THE DSCNT GIVEN TO THE FGT PLT WHICH WAS OK UNTIL TRNEE TURNED ACFT TOWARDS EACH OTHER.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.