Narrative:

Ny approach, upon initial check-in, cleared us direct to teb VOR and said expect ILS runway 22R at newark. 4 NM north of ayron, at 3000 ft MSL, proceeding direct to teterboro VOR, ny approach issued a heading to 'intercept the localizer for runway 22R, descend to 2500 ft MSL, and cleared for the approach.' the proper frequency was tuned into the localizer and the approach set up for the ILS runway 22R at ewr. The aircraft was configured and, finally, the localizer frequency were idented. The aircraft was stable at 1000 ft AGL, we broke out at 2500 ft MSL and visually idented runway 22R at newark. The raw data of the ILS agreed with the visual indications. While on short final, tower asked us to identify the frequency for runway 22R for a correct identify code, after we landed. Landing was uneventful. On the ground, the ILS identify did not match the current code shown on the current approach page. Human performance: rushed, late in the approach, fatigue, all indications of approach agreed with ILS system. Corrective action: ILS system may be intermittent and erratic. Callback conversation with reporter revealed the following information: reporter advises he was so on the flight and had no direct involvement in the identify process. He stated that several flts had reported the anomaly and that the captain had appeared to have checked the identify as a result. The tower asked them, on short final, to verify the identify and they refused until the approach and landing was completed. At that time the identify was incorrect but the reporter could not specify what code was being broadcast. Reporter further advises that the approach was made in predominately VMC conditions and that cockpit workload precluded the identify from being a major priority since the indications were correct and the runway was in sight well outside the OM.

Google
 

Original NASA ASRS Text

Title: WHEN ASKED BY TWR TO VERIFY IT, FLT CREW OF B727-200 FOUND ILS RWY 22R AT EWR BROADCASTING INCORRECT IDENT CODE. ALL OTHER ACFT INDICATIONS NORMAL AND THE NAV FACILITY WAS GIVING ACCURATE AND APPROPRIATE COURSE AND GS INDICATIONS.

Narrative: NY APCH, UPON INITIAL CHK-IN, CLRED US DIRECT TO TEB VOR AND SAID EXPECT ILS RWY 22R AT NEWARK. 4 NM N OF AYRON, AT 3000 FT MSL, PROCEEDING DIRECT TO TETERBORO VOR, NY APCH ISSUED A HEADING TO 'INTERCEPT THE LOC FOR RWY 22R, DSND TO 2500 FT MSL, AND CLRED FOR THE APCH.' THE PROPER FREQ WAS TUNED INTO THE LOC AND THE APCH SET UP FOR THE ILS RWY 22R AT EWR. THE ACFT WAS CONFIGURED AND, FINALLY, THE LOC FREQ WERE IDENTED. THE ACFT WAS STABLE AT 1000 FT AGL, WE BROKE OUT AT 2500 FT MSL AND VISUALLY IDENTED RWY 22R AT NEWARK. THE RAW DATA OF THE ILS AGREED WITH THE VISUAL INDICATIONS. WHILE ON SHORT FINAL, TWR ASKED US TO IDENT THE FREQ FOR RWY 22R FOR A CORRECT IDENT CODE, AFTER WE LANDED. LNDG WAS UNEVENTFUL. ON THE GND, THE ILS IDENT DID NOT MATCH THE CURRENT CODE SHOWN ON THE CURRENT APCH PAGE. HUMAN PERFORMANCE: RUSHED, LATE IN THE APCH, FATIGUE, ALL INDICATIONS OF APCH AGREED WITH ILS SYS. CORRECTIVE ACTION: ILS SYS MAY BE INTERMITTENT AND ERRATIC. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR ADVISES HE WAS SO ON THE FLT AND HAD NO DIRECT INVOLVEMENT IN THE IDENT PROCESS. HE STATED THAT SEVERAL FLTS HAD RPTED THE ANOMALY AND THAT THE CAPT HAD APPEARED TO HAVE CHKED THE IDENT AS A RESULT. THE TWR ASKED THEM, ON SHORT FINAL, TO VERIFY THE IDENT AND THEY REFUSED UNTIL THE APCH AND LNDG WAS COMPLETED. AT THAT TIME THE IDENT WAS INCORRECT BUT THE RPTR COULD NOT SPECIFY WHAT CODE WAS BEING BROADCAST. RPTR FURTHER ADVISES THAT THE APCH WAS MADE IN PREDOMINATELY VMC CONDITIONS AND THAT COCKPIT WORKLOAD PRECLUDED THE IDENT FROM BEING A MAJOR PRIORITY SINCE THE INDICATIONS WERE CORRECT AND THE RWY WAS IN SIGHT WELL OUTSIDE THE OM.

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.