TWR ALERTED FLC OF LOW ALT ALERT WHEN THEY WERE ON ILS APCH. PF'S GS INDICATED FULL UP CORRECTION; BUT THE #2 INDICATED ON GS. THE #2 WAS INOP. AFTER THE ALERT THE PF CORRECTED FOR AN UNEVENTFUL LNDG.

1996-05 · NASA ASRS report 337130

Date: 1996-05 · Aircraft: Any Unknown or Unlisted Aircraft Manufacturer · Phase: approach

Anomalies: aircraft-equipment-problem-critical|deviation-altitude-overshoot|deviation-discrepancy-procedural-clearance|deviation-discrepancy-procedural-published-material-policy|inflight-event-encounter-cftt-cfit

Synopsis

TWR ALERTED FLC OF LOW ALT ALERT WHEN THEY WERE ON ILS APCH. PF'S GS INDICATED FULL UP CORRECTION; BUT THE #2 INDICATED ON GS. THE #2 WAS INOP. AFTER THE ALERT THE PF CORRECTED FOR AN UNEVENTFUL LNDG.

Narrative

TWR (LCL CTL) ADVISED OF AN ALT ALERT AND INFORMED THAT THE MINIMUM INST ALT FOR OUR LOCATION WAS 1300 FT MSL. THE TWR OF COURSE WAS CORRECT; HOW DID THIS OCCUR? ORF WAS NOT THE ORIGINAL DEST. IT WAS IN FACT THE THIRD ARPT UTILIZED; THE ONLY WITH AN ILS. THE FIRST ARPT WAS SFQ. THIS WAS THE ORIGINAL DEST. HOWEVER; UPON ARR; THE ONLY APCH NAVAID (NDB) WAS INOP. APCH CTL WAS NOT AWARE THE FACILITY WAS INOP AND THERE WERE NO NOTAMS TO THAT EFFECT. NOTAM INFO WAS CAREFULLY CHKED BEFORE DEP FROM KINSTON; NC. THE FLT DIVERTED TO CPK FOR THE LOC 5 APCH. 2 APCHS WERE MADE AT CPK; BOTH ENDING IN MISSED APCHS. SEVERAL INTERESTING ITEMS ABOUT THE CPK ARPT/APCH: 1) THE RWY LIGHTS REMAIN ON THE OLD CTAF OF 122.7 WHILE THE NEW CTAF OF 123.05 IS NOTAMED VIA THE AWOS. OF COURSE THE ENTIRE INFO IS A LCL AND NOT A DISTANT NOTAM. YET THE AWOS VERBALLY TELLS YOU TO USE 123.05 AS THE CTAF AND IS MUTE ON THE DIFFERENT FREQ FOR RWY LIGHTS. 2) THE LOC RWY 5 APCH PLATE FOR CPK IDENTS THE NDB IDENT AS 'EYK' (CHESI). HOWEVER; THE ACFT WAS RECEIVING 'EY;' NO 'K' WAS BEING RECEIVED. THIS NOW IS THE SECOND NDB NAVAID WITH RECEPTION PROBS. THE FLT DIVERTED TO ORF FOR THE ILS RWY 5. THE ACFT IS EQUIPPED WITH 2 ILS RECEIVERS; EACH WITH GS. UPON RECEIVING APCH CLRNC WE BECAME ESTABLISHED ON THE LOC AND HANDED OFF TO TWR. WE WERE INSIDE 'CALEY;' HAD A FULL UP GS ON NAV #1; A CTRED GS ON NAV #2; AND AN ADF BEARING TOWARD THE TAIL. ANALYSIS (FAULTY) INSIDE FAF (INGLE) AND ON GLIDE PATH. THE TRUTH WAS GS #2 WAS INOP. GS #1 WAS ACCURATE AND THE ADF WAS NOT WORKING PROPERLY. SINCE WE WERE WELL ABOVE THE MDA FOR THE APCH I HAD NOT INTERVENED; AND THE PIC SALVAGED THE APCH TO AN UNEVENTFUL CONCLUSION. CONTRIBUTING FACTORS: 1) SUFFOLK; VA; NDB IS NOT IDENTED AS UNMONITORED IF THE GND XMITTER WAS INOP (WHICH IT WAS AND HAD BEEN BEFORE WE DEPARTED KINSTON; NC). THE APCH PLATE SHOULD ADVISE AS UNMONITORED. 2) CHESAPEAKE; VA; LOC RWY 5 APCH PLATE IDENTS THE CTAF AS 122.7 AND INSTRUCTS TO ACTIVATE LIGHTING ON 122.7. HOWEVER; THE AWOS INSTRUCTIONS NOTAM THE CTAF TO 123.05 AND IS MUTE ON THE LIGHTING. THIS IS A LCL NOTAM VIA FSS AND IF ONE HAD RECEIVED THE FSS LCL NOTAM AND SUBSEQUENTLY RECEIVED THE NOTAM VIA AWOS; WHICH FREQ FOR LIGHTING WOULD BE THE MOST CURRENT? WHY IS THE ARPT LIGHTING FREQ NOT PART OF THE AWOS NOTAM INFO? P.S. WHY IS CPK PARACHUTE JUMPING ACTIVITIES LISTED AS A LCL NOTAM FOR NORFOLK? 3) CHESI (EYK) NDB IDENTIFIER SHOWN ON THE APCH PLATE SHOULD BE ACCURATE; OR AT LEAST NOTAMED UNTIL THE PLATE OR THE XMITTER IS CORRECTED. CORRECTIVE ACTIONS: 1) THE PIC LEARNED TO VERIFY GS INTERCEPT ALT SHOWN ON THE APCH PLATE. 2) THE MARKER BEACON SYS WAS WORKING AND OBVIOUSLY THE ADF SYS WAS INACCURATE. 3) WHEN AN ERROR EXISTS BTWN 2 INSTS (GS); INVESTIGATE RATHER THAN ASSUME. NEED TO UTILIZE ALL OR AT LEAST ADDITIONAL INFO PRIOR TO FINAL DETERMINATION.

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

Loading the flight search…

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.