Military B1 spillout from MOA.

Attributes
ACN	295436
Time
Date	199501
Day	Mon
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : bam
State Reference	NV
Altitude	msl bound lower : 28000 msl bound upper : 28000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zlc military facility : nfl tower : mdw
Operator	other
Make Model Name	B1 Lancer
Operating Under FAR Part	other : other
Flight Phase	cruise other
Route In Use	enroute : direct
Flight Plan	VFR
Person 1
Affiliation	government : faa
Function	controller : radar
Qualification	controller : radar
ASRS Report	295436
Person 2
Affiliation	government : military
Function	controller : approach
Qualification	controller : military
Events
Anomaly	non adherence : published procedure other anomaly other
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance other
Consequence	Other
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

I was working ZLC sector 43 which is sfc to FL310. Fallon NAS (desert control) attempted to head off military X (H/B1). I could not see the aircraft. The aircraft was under fallon control working the gabbs and austin atcaa FL280 and below. The controller at fallon told me X would be going into austin 1 at FL280 and would be my control. Aircraft came out of fallon's airspace heading towards ilc which is contrary to what I was told. X was not showing up on my radar for some reason. I had air carrier Y a B737 slc...mja, MADN3, oak at FL350. I got a position on X and from his position I determined X had exited fallon's airspace and was close to air carrier Y position. I descended X to FL270. I then issued a heading to get X back into fallon's airspace to get radar contact. I finally established radar on X and cleared X on course. I called the fallon controller to see what had gone wrong. The fallon controller told me he had told the B-1 to 'maintain VFR eastbound.' I told him that as soon as X left their airspace he would be IFR in positive controled airspace. The controller at fallon told me he could not stop X from going VFR. I explained to him that at FL280 in positive controled airspace X was not VFR!

Original NASA ASRS Text

Title: MIL B1 SPILLOUT FROM MOA.

Narrative: I WAS WORKING ZLC SECTOR 43 WHICH IS SFC TO FL310. FALLON NAS (DESERT CTL) ATTEMPTED TO HEAD OFF MIL X (H/B1). I COULD NOT SEE THE ACFT. THE ACFT WAS UNDER FALLON CTL WORKING THE GABBS AND AUSTIN ATCAA FL280 AND BELOW. THE CTLR AT FALLON TOLD ME X WOULD BE GOING INTO AUSTIN 1 AT FL280 AND WOULD BE MY CTL. ACFT CAME OUT OF FALLON'S AIRSPACE HEADING TOWARDS ILC WHICH IS CONTRARY TO WHAT I WAS TOLD. X WAS NOT SHOWING UP ON MY RADAR FOR SOME REASON. I HAD ACR Y A B737 SLC...MJA, MADN3, OAK AT FL350. I GOT A POS ON X AND FROM HIS POS I DETERMINED X HAD EXITED FALLON'S AIRSPACE AND WAS CLOSE TO ACR Y POS. I DSNDED X TO FL270. I THEN ISSUED A HDG TO GET X BACK INTO FALLON'S AIRSPACE TO GET RADAR CONTACT. I FINALLY ESTABLISHED RADAR ON X AND CLRED X ON COURSE. I CALLED THE FALLON CTLR TO SEE WHAT HAD GONE WRONG. THE FALLON CTLR TOLD ME HE HAD TOLD THE B-1 TO 'MAINTAIN VFR EBOUND.' I TOLD HIM THAT AS SOON AS X LEFT THEIR AIRSPACE HE WOULD BE IFR IN POSITIVE CTLED AIRSPACE. THE CTLR AT FALLON TOLD ME HE COULD NOT STOP X FROM GOING VFR. I EXPLAINED TO HIM THAT AT FL280 IN POSITIVE CTLED AIRSPACE X WAS NOT VFR!

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.