#2 ILS VOR changed on air carrier aircraft after write-up was interpreted as #2. #1 was actually ino...

Attributes
ACN	131620
Time
Date	198912
Day	Mon
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : hpn
State Reference	NY
Altitude	agl bound lower : 0 agl bound upper : 0
Aircraft 1
Controlling Facilities	tower : orf
Operator	common carrier : air carrier
Make Model Name	Medium Large Transport, Low Wing, 2 Turbojet Eng
Flight Phase	ground : parked other
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	other personnel other oversight : supervisor
Qualification	other other : other
ASRS Report	131620
Person 2
Affiliation	company : air carrier
Function	other personnel other
Qualification	other other : other
Events
Anomaly	aircraft equipment problem : less severe non adherence : far other anomaly other
Independent Detector	other other : unspecified
Resolutory Action	none taken : detected after the fact
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation other

Narrative:

Air carrier reported to me (maintenance controller) via arinc that #1 ILS system was inoperative. Lga mechanic was assigned to work the #1 ILS system. Mechanic arrived at hpn, worked an airplane and reported to me that job was completed and signed off. I asked for details of fix and was informed #2 VOR/ILS receiver was replaced. I advised the lga mechanic that #1 system was reported to me by arinc contact with crew. He stated it was impossible to determine what system was inoperative because the logbook writing was illegible. He read report as copilot's (#2 system) as inoperative. He replaced #2 VOR/ILS receiving, tested both systems with VOR/ILS tester and cleared report. Airplane flew to ord with inbound report #1 ILS was inoperative. Subsequent corrective action was resecure receiver in radio rack account found loose. The major factor contributing to not fixing this system was the illegible log book writing. Better communication between myself and mechanic who worked the job and crew certainly would have helped.

Original NASA ASRS Text

Title: #2 ILS VOR CHANGED ON ACR ACFT AFTER WRITE-UP WAS INTERPRETED AS #2. #1 WAS ACTUALLY INOPERATIVE, BUT WRITING WAS TOO ILLEGIBLE TO MAKE CLEAR DETERMINATION.

Narrative: ACR RPTED TO ME (MAINT CTLR) VIA ARINC THAT #1 ILS SYS WAS INOP. LGA MECH WAS ASSIGNED TO WORK THE #1 ILS SYS. MECH ARRIVED AT HPN, WORKED AN AIRPLANE AND RPTED TO ME THAT JOB WAS COMPLETED AND SIGNED OFF. I ASKED FOR DETAILS OF FIX AND WAS INFORMED #2 VOR/ILS RECEIVER WAS REPLACED. I ADVISED THE LGA MECH THAT #1 SYS WAS RPTED TO ME BY ARINC CONTACT WITH CREW. HE STATED IT WAS IMPOSSIBLE TO DETERMINE WHAT SYS WAS INOP BECAUSE THE LOGBOOK WRITING WAS ILLEGIBLE. HE READ RPT AS COPLT'S (#2 SYS) AS INOP. HE REPLACED #2 VOR/ILS RECEIVING, TESTED BOTH SYSTEMS WITH VOR/ILS TESTER AND CLRED RPT. AIRPLANE FLEW TO ORD WITH INBND RPT #1 ILS WAS INOP. SUBSEQUENT CORRECTIVE ACTION WAS RESECURE RECEIVER IN RADIO RACK ACCOUNT FOUND LOOSE. THE MAJOR FACTOR CONTRIBUTING TO NOT FIXING THIS SYS WAS THE ILLEGIBLE LOG BOOK WRITING. BETTER COM BTWN MYSELF AND MECH WHO WORKED THE JOB AND CREW CERTAINLY WOULD HAVE HELPED.

Data retrieved from NASA's ASRS site as of August 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.

#2 ILS VOR changed on air carrier aircraft after write-up was interpreted as #2. #1 was actually inoperative, but writing was too illegible to make clear determination.