37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 800072 |
Time | |
Date | 200808 |
Place | |
Locale Reference | atc facility : jnu.fss |
State Reference | AK |
Person 1 | |
Affiliation | government : faa |
Function | controller : flight data |
Experience | controller time certified in position1 : 26.7 flight time total : 300 |
ASRS Report | 800072 |
Events | |
Independent Detector | other other : 1 |
Resolutory Action | none taken : anomaly accepted |
Supplementary | |
Problem Areas | FAA |
Primary Problem | FAA |
Narrative:
While working preflight 6; I received a call from aircraft X requesting to close his flight plan. Aircraft X was on the ground at mri. Ena did not hold a flight plan on aircraft X. I made an entry into our daily facility log as controller in charge after reviewing the tapes and confirmed jnu AFSS did not activate the flight plan. I was retaliated and harassed for making the entry the next day by a supervisor. The entry was reviewed by a supervisor and was determined to be a flight plan number (error) and fpno was written beside my entry in the facility log. Several days later; the added entry by the supervisor was removed and the quality review stated no error. Multiple times errors are not reported because of retaliation and harassment. Quality reviews are being reported as a non event. My concern is that tapes/documents/recordings will be discarded after 45 days and no one will know the difference. Errors discovered at jnu AFSS have been documented at our facility as non events with no documentation of the errors at jnu tower/zan; or anchorage regional office. The culture of non reporting errors has become standard business.
Original NASA ASRS Text
Title: JNU AFSS CTLR VOICED CONCERN REGARDING OPERROR REPORTING; CLAIMING FACILITY COVER-UP OF SAME.
Narrative: WHILE WORKING PREFLT 6; I RECEIVED A CALL FROM ACFT X REQUESTING TO CLOSE HIS FLT PLAN. ACFT X WAS ON THE GND AT MRI. ENA DID NOT HOLD A FLT PLAN ON ACFT X. I MADE AN ENTRY INTO OUR DAILY FACILITY LOG AS CIC AFTER REVIEWING THE TAPES AND CONFIRMED JNU AFSS DID NOT ACTIVATE THE FLT PLAN. I WAS RETALIATED AND HARASSED FOR MAKING THE ENTRY THE NEXT DAY BY A SUPVR. THE ENTRY WAS REVIEWED BY A SUPVR AND WAS DETERMINED TO BE A FLT PLAN NUMBER (ERROR) AND FPNO WAS WRITTEN BESIDE MY ENTRY IN THE FACILITY LOG. SEVERAL DAYS LATER; THE ADDED ENTRY BY THE SUPVR WAS REMOVED AND THE QUALITY REVIEW STATED NO ERROR. MULTIPLE TIMES ERRORS ARE NOT RPTED BECAUSE OF RETALIATION AND HARASSMENT. QUALITY REVIEWS ARE BEING RPTED AS A NON EVENT. MY CONCERN IS THAT TAPES/DOCUMENTS/RECORDINGS WILL BE DISCARDED AFTER 45 DAYS AND NO ONE WILL KNOW THE DIFFERENCE. ERRORS DISCOVERED AT JNU AFSS HAVE BEEN DOCUMENTED AT OUR FACILITY AS NON EVENTS WITH NO DOCUMENTATION OF THE ERRORS AT JNU TWR/ZAN; OR ANCHORAGE REGIONAL OFFICE. THE CULTURE OF NON RPTING ERRORS HAS BECOME STANDARD BUSINESS.
Data retrieved from NASA's ASRS site as of May 2009 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.