ZAN Controller described an event when an aircraft was cleared for a RNAV(GPS) Runway 36 to SNP when it was unusable; reporter alleged current procedure status information distribution is inadequate for both controller's and user's.

Date: 2009-11 · Aircraft: Light Transport; Low Wing; 2 Turboprop Eng · Phase: approach

Anomalies: atc-issue-all-types|deviation-discrepancy-procedural-other-unknown

Synopsis

ZAN Controller described an event when an aircraft was cleared for a RNAV(GPS) Runway 36 to SNP when it was unusable; reporter alleged current procedure status information distribution is inadequate for both controller's and user's.

Narrative

Aircraft departed ZZZ; headed for SNP; and asked for a RNAV(GPS) RY 36; which I gave. They had the NOTAMS and local WX and had gotten into ZZZ on a visual approach and had canceled IFR out of 4500 ft at ZZZ so weather was good. I was distracted with another issue with ATOP on and aircraft out of conformance and possible CPAR failure en-route to SYA from sector 13 so I forgot the RNAV (GPS) 18 and 36 was unusable from another abnormality; though it was listed on the outage sheet (green screen) as failed. It can't fail; but the listing does not list unusable only failed or OTS. The aircraft landed and canceled on the ground without incident; but it could have been an issue. The pilot should have had all the information; but must have missed the notice too. Recommendation; we need better and thorough notification of what's out and unusable to ensure the pilots know too. A RNAV (GPS) approach does not fail; but could be unusable for an abnormality and needs to be treated as such and listed as such.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.