ZAB controller described inadvertent MOA entry by an IFR aircraft being provided service. Reporter i...

Narrative:

I observed aircraft X slightly in the mt. Dora MOA. I told the r-side. The r-side immediately turned the aircraft out of the MOA. The military aircraft in the MOA were in the south end and were tracking north bound. The r-side tried to get a hold of the military flight on our frequency and on 243.0 ( emergency frequency) but was unable to reach them. Prior to the military aircraft getting within 15 miles of aircraft X he had exited the MOA on a heading given by the radar controller. The route of flight assigned to aircraft X on the electronic strip was cos..dht.V81.lbb.; this routing would have kept him clear of the MOA. The aircraft said he was given direct lbb by the denver center sector D41 controller. We did not verify this with D41. Recommendation; the D41 controller should have put this in the computer to reflect what aircraft X was doing and it would have alerted in uret to let them and us know that he was heading for the MOA. There is a procedure for sector 15 to alert denver sector 41 when mt. Dora is in use. We did alert D41 that mt. Dora was in use. An other way to alert controllers of a possible conflict would be to have an aircraft alert to an active airspace by their track across the ground and not just their routing in the computer.

Original NASA ASRS Text

Title: ZAB Controller described inadvertent MOA entry by an IFR aircraft being provided service. Reporter indicated routing had been changed by the previous sector but not reflected in the computer and/or verbally coordinated.

Narrative: I observed Aircraft X slightly in the Mt. Dora MOA. I told the R-Side. The R-Side immediately turned the aircraft out of the MOA. The Military aircraft in the MOA were in the South end and were tracking North bound. The R-Side tried to get a hold of the Military flight on our frequency and on 243.0 ( emergency frequency) but was unable to reach them. Prior to the Military aircraft getting within 15 miles of Aircraft X he had exited the MOA on a heading given by the RADAR Controller. The route of flight assigned to Aircraft X on the electronic strip was COS..DHT.V81.LBB.; this routing would have kept him clear of the MOA. The aircraft said he was given direct LBB by the Denver Center Sector D41 Controller. WE did not verify this with D41. Recommendation; the D41 controller should have put this in the computer to reflect what Aircraft X was doing and it would have alerted in URET to let them and us know that he was heading for the MOA. There is a procedure for Sector 15 to alert Denver Sector 41 when Mt. Dora is in use. We did alert D41 that Mt. Dora was in use. An other way to alert controllers of a possible conflict would be to have an aircraft alert to an active airspace by their track across the ground and not just their routing in the computer.

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

Attributes
ACN	869671
Time
Date	201001
Local Time Of Day	1801-2400
Place
Locale Reference	ZAB.ARTCC
State Reference	NM
Aircraft 1
Make Model Name	PA-31 Navajo/Chieftan/Mojave/T1040
Flight Phase	Cruise
Route In Use	Direct
Flight Plan	IFR
Person 1
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Deviation - Procedural Published Material / Policy

ZAB controller described inadvertent MOA entry by an IFR aircraft being provided service. Reporter indicated routing had been changed by the previous sector but not reflected in the computer and/or verbally coordinated.