Fgt operating in a restricted area at a higher altitude than indicated for active airspace.

Attributes
ACN	238090
Time
Date	199304
Day	Fri
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : zid
State Reference	IN
Altitude	msl bound lower : 30000 msl bound upper : 40000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zid
Operator	other
Make Model Name	Fighter
Flight Phase	cruise other
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : radar
Qualification	controller : radar
Experience	controller non radar : 3 controller radar : 4
ASRS Report	238090
Person 2
Affiliation	government : military
Function	flight crew : single pilot
Qualification	pilot : military
Events
Anomaly	airspace violation : exit other anomaly other
Independent Detector	other controllera
Resolutory Action	none taken : detected after the fact
Consequence	Other
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Intra Facility Coordination Failure other

Narrative:

I assumed duties as radar controller at the covington low sector at XD04Z. Fgt X flight was operating in R5503A between 4500 ft and FL400 as previously cleared by the last controller. At approximately XD30Z my data controller noticed that the military desk was indicating that R5503 was active FL300 and below. Fgt X would not respond to repeated xmissions and area supervisor was notified. Fgt X was then observed to exit the confines of R5503A and came up on another frequency indicating that his wing man had a mechanical problem and he was escorting him back to tol. During this, MTR B entered R5503A at FL270 without permission (we were the controling agency) made 1 turn and exited. Our investigation shows that the previous radar controller at covington low had assigned fgt X the block altitude he had requested per the airspace usage schedule at the sector (attached). This sector and control of R5503 was transferred to our area of specialization just this week and apparently there are no written procedures covering sits like this. I.e., the schedule says one thing which the controller uses, and what the military area desk puts out to the rest of the center. While there were no apparent operrors, this was a very dangerous situation with 2 fgt's engaged in air combat maneuver operation 10000 ft above the top of the restr area.

Original NASA ASRS Text

Title: FGT OPERATING IN A RESTRICTED AREA AT A HIGHER ALT THAN INDICATED FOR ACTIVE AIRSPACE.

Narrative: I ASSUMED DUTIES AS RADAR CTLR AT THE COVINGTON LOW SECTOR AT XD04Z. FGT X FLT WAS OPERATING IN R5503A BTWN 4500 FT AND FL400 AS PREVIOUSLY CLRED BY THE LAST CTLR. AT APPROX XD30Z MY DATA CTLR NOTICED THAT THE MIL DESK WAS INDICATING THAT R5503 WAS ACTIVE FL300 AND BELOW. FGT X WOULD NOT RESPOND TO REPEATED XMISSIONS AND AREA SUPVR WAS NOTIFIED. FGT X WAS THEN OBSERVED TO EXIT THE CONFINES OF R5503A AND CAME UP ON ANOTHER FREQ INDICATING THAT HIS WING MAN HAD A MECHANICAL PROB AND HE WAS ESCORTING HIM BACK TO TOL. DURING THIS, MTR B ENTERED R5503A AT FL270 WITHOUT PERMISSION (WE WERE THE CTLING AGENCY) MADE 1 TURN AND EXITED. OUR INVESTIGATION SHOWS THAT THE PREVIOUS RADAR CTLR AT COVINGTON LOW HAD ASSIGNED FGT X THE BLOCK ALT HE HAD REQUESTED PER THE AIRSPACE USAGE SCHEDULE AT THE SECTOR (ATTACHED). THIS SECTOR AND CTL OF R5503 WAS TRANSFERRED TO OUR AREA OF SPECIALIZATION JUST THIS WK AND APPARENTLY THERE ARE NO WRITTEN PROCS COVERING SITS LIKE THIS. I.E., THE SCHEDULE SAYS ONE THING WHICH THE CTLR USES, AND WHAT THE MIL AREA DESK PUTS OUT TO THE REST OF THE CTR. WHILE THERE WERE NO APPARENT OPERRORS, THIS WAS A VERY DANGEROUS SIT WITH 2 FGT'S ENGAGED IN AIR COMBAT MANEUVER OP 10000 FT ABOVE THE TOP OF THE RESTR AREA.

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.