37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 956716 |
Time | |
Date | 201107 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZOA.ARTCC |
State Reference | CA |
Aircraft 1 | |
Make Model Name | Cessna Stationair/Turbo Stationair 6 |
Flight Phase | Cruise |
Flight Plan | IFR |
Person 1 | |
Function | Enroute |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types |
Narrative:
Sector 45/46 combined. I took sector and during position relief briefing; aircraft X was discussed. Victor 32 is good at 110; V6 is good at 120. Aircraft X was at 110 and this was the route in uret. Even after the prb was over; the relieved controller and I looked at our overhead map and verified the route and altitude were good. During the flight; I issued the lol altimeter prior to llc VORTAC. When aircraft X reached llc VORTAC; I shipped him to zcu 43 with a clear and correct read back. My attention was all over both sectors 45 and 46 with navy fallon approach airspace opening; and aircraft inbound prior to their open time; VFR pop-ups; hand-offs; point-outs; traffic counts; separation of inbound and outbound aircraft to reno area airports...no down time; but continual work load. Aircraft X was south of course; zcu had control for turns; so this did not prompt any action. I dropped the data block when aircraft X was in zcu 43's airspace. The zcu 43 controller called and asked for me to try aircraft X again; he was heading for a 120 box. I informed him that he was shipped at llc and responded. I remember seeing a different code on an aircraft going into zcu 43's airspace and asked if he had changed code on aircraft X. That was not the case. I transmitted for the aircraft without response; the aircraft was in a position and altitude that my radios do not cover. I pulled the flight plan up on uret using the beacon code; it still showed V32. I kept the flight plan in uret to discuss with the supervisor. I tried aircraft X on my 2 transmitter sights and also guard frequency. Zcu 43 sent an aircraft back to my frequency to try to raise aircraft X with no response. The supervisor ran a sprt that showed the aircraft on V6 which is what he flew. This raises several questions. 1. Why does NAS via sprt show a different route than uret; not a new problem at ZOA? 2. Why did the zcu 43 controller wait so long to question the route; altitude; and NORDO aircraft? 3. The pilot has a responsibility to fly in compliance with the mia of an airway; but did not. 4. Why didn't an MSAW alert go off in my airspace? Recommendation: fix uret/NAS flight plan problems.
Original NASA ASRS Text
Title: ZOA Controller described a probable MIA infraction after transferring an aircraft to an adjacent sector; the reporter questioning the validity of URET routing information.
Narrative: Sector 45/46 combined. I took sector and during position relief briefing; Aircraft X was discussed. Victor 32 is good at 110; V6 is good at 120. Aircraft X was at 110 and this was the route in URET. Even after the PRB was over; the relieved controller and I looked at our overhead map and verified the route and altitude were good. During the flight; I issued the LOL altimeter prior to LLC VORTAC. When Aircraft X reached LLC VORTAC; I shipped him to ZCU 43 with a clear and correct read back. My attention was all over both Sectors 45 and 46 with Navy Fallon Approach airspace opening; and aircraft inbound prior to their open time; VFR pop-ups; hand-offs; point-outs; traffic counts; separation of inbound and outbound aircraft to Reno area airports...no down time; but continual work load. Aircraft X was South of course; ZCU had control for turns; so this did not prompt any action. I dropped the Data Block when Aircraft X was in ZCU 43's airspace. The ZCU 43 Controller called and asked for me to try Aircraft X again; he was heading for a 120 box. I informed him that he was shipped at LLC and responded. I remember seeing a different code on an aircraft going into ZCU 43's airspace and asked if he had changed code on Aircraft X. That was not the case. I transmitted for the aircraft without response; the aircraft was in a position and altitude that my radios do not cover. I pulled the flight plan up on URET using the beacon code; it still showed V32. I kept the flight plan in URET to discuss with the supervisor. I tried Aircraft X on my 2 transmitter sights and also Guard frequency. ZCU 43 sent an aircraft back to my frequency to try to raise Aircraft X with no response. The supervisor ran a SPRT that showed the aircraft on V6 which is what he flew. This raises several questions. 1. Why does NAS via SPRT show a different route than URET; not a new problem at ZOA? 2. Why did the ZCU 43 controller wait so long to question the route; altitude; and NORDO aircraft? 3. The pilot has a responsibility to fly in compliance with the MIA of an airway; but did not. 4. Why didn't an MSAW alert go off in my airspace? Recommendation: fix URET/NAS flight plan problems.
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.