Narrative:

The safety item at issue here is airline X filing of rtes through MOA's. The specific route is the cvg direct air route that penetrates the buckeye MOA just southeast of dayton, oh. This has been a continuous problem for over 6 months. I spoke with our traffic management officer back in mar/99. He advised me that they shared our safety concerns and that they had already spoken to airline X about it. In his words, 'we're already on that...it's been taken care of.' I was also informed at that time, that airlines could legally file through MOA's under the guise of nrp, but could not file through restr areas. Even though the buckeye MOA is known to be in use FL500 and below daily, airline X still files rtes through it. The fact that someone in a staff capacity even differentiated between the 2 is ridiculous. If sua is 'hot,' then controllers must keep aircraft laterally separated from it. It doesn't matter in a practical workload sense whether it's a restr area or an MOA. As you might guess, there certainly is a greater potential for error here. Aside from the obvious situation of a NORDO aircraft, controllers must issue and monitor vectors around the sua. This increases workload! Now, combine that with the fact that nrp flts already increase workload and complexity because of their nonstandard nature, and you have an even greater chance for error. Callback conversation with reporter revealed the following information: controller is concerned with the additional sector workload caused at times when nrp routings conflict with MOA usage. Controller was unable to obtain satisfaction via facility and national grievance procedures. Controller wants the airlines to file around all MOA/restr areas and will issue 'direct clrncs' as work conditions permit. Analyst recognizes that this change would substantially change the concept of nrp, placing traffic management back to where user challenges to timely airspace usage began a number of yrs ago.

Google
 

Original NASA ASRS Text

Title: ZID CTLR CONCERNED WITH AIRLINES, ON NRP ROUTINGS, FILING THROUGH THE BUCKEYE MOA. PENDING THE TIME OF DAY AND MOA SCHEDULING, ACFT MUST BE VECTORED AROUND THE MOA BEFORE BEING CLRED ON COURSE.

Narrative: THE SAFETY ITEM AT ISSUE HERE IS AIRLINE X FILING OF RTES THROUGH MOA'S. THE SPECIFIC RTE IS THE CVG DIRECT AIR RTE THAT PENETRATES THE BUCKEYE MOA JUST SE OF DAYTON, OH. THIS HAS BEEN A CONTINUOUS PROB FOR OVER 6 MONTHS. I SPOKE WITH OUR TFC MGMNT OFFICER BACK IN MAR/99. HE ADVISED ME THAT THEY SHARED OUR SAFETY CONCERNS AND THAT THEY HAD ALREADY SPOKEN TO AIRLINE X ABOUT IT. IN HIS WORDS, 'WE'RE ALREADY ON THAT...IT'S BEEN TAKEN CARE OF.' I WAS ALSO INFORMED AT THAT TIME, THAT AIRLINES COULD LEGALLY FILE THROUGH MOA'S UNDER THE GUISE OF NRP, BUT COULD NOT FILE THROUGH RESTR AREAS. EVEN THOUGH THE BUCKEYE MOA IS KNOWN TO BE IN USE FL500 AND BELOW DAILY, AIRLINE X STILL FILES RTES THROUGH IT. THE FACT THAT SOMEONE IN A STAFF CAPACITY EVEN DIFFERENTIATED BTWN THE 2 IS RIDICULOUS. IF SUA IS 'HOT,' THEN CTLRS MUST KEEP ACFT LATERALLY SEPARATED FROM IT. IT DOESN'T MATTER IN A PRACTICAL WORKLOAD SENSE WHETHER IT'S A RESTR AREA OR AN MOA. AS YOU MIGHT GUESS, THERE CERTAINLY IS A GREATER POTENTIAL FOR ERROR HERE. ASIDE FROM THE OBVIOUS SIT OF A NORDO ACFT, CTLRS MUST ISSUE AND MONITOR VECTORS AROUND THE SUA. THIS INCREASES WORKLOAD! NOW, COMBINE THAT WITH THE FACT THAT NRP FLTS ALREADY INCREASE WORKLOAD AND COMPLEXITY BECAUSE OF THEIR NONSTANDARD NATURE, AND YOU HAVE AN EVEN GREATER CHANCE FOR ERROR. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: CTLR IS CONCERNED WITH THE ADDITIONAL SECTOR WORKLOAD CAUSED AT TIMES WHEN NRP ROUTINGS CONFLICT WITH MOA USAGE. CTLR WAS UNABLE TO OBTAIN SATISFACTION VIA FACILITY AND NATL GRIEVANCE PROCS. CTLR WANTS THE AIRLINES TO FILE AROUND ALL MOA/RESTR AREAS AND WILL ISSUE 'DIRECT CLRNCS' AS WORK CONDITIONS PERMIT. ANALYST RECOGNIZES THAT THIS CHANGE WOULD SUBSTANTIALLY CHANGE THE CONCEPT OF NRP, PLACING TFC MGMNT BACK TO WHERE USER CHALLENGES TO TIMELY AIRSPACE USAGE BEGAN A NUMBER OF YRS AGO.

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.