37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 540401 |
Time | |
Date | 200203 |
Day | Wed |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : zzz.airport |
State Reference | IL |
Altitude | agl single value : 0 |
Environment | |
Light | Daylight |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | Fokker 100 |
Operating Under FAR Part | Part 121 |
Flight Phase | ground : parked |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
ASRS Report | 540401 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Events | |
Anomaly | maintenance problem : improper documentation non adherence : company policies non adherence : published procedure other anomaly other |
Independent Detector | other other : 4 mntnc |
Resolutory Action | none taken : detected after the fact |
Consequence | other |
Supplementary | |
Problem Areas | Flight Crew Human Performance Maintenance Human Performance Cabin Crew Human Performance Company Aircraft |
Primary Problem | Company |
Narrative:
I was the captain of the referenced flight. I received a courtesy call (voice mail) from another captain who was scheduled to fly the same aircraft later the same day. He advised me that a mechanic at ord noticed that the security check paperwork generated by ZZZ1 referenced nose number XXX instead of yxx. The aircraft was flown by 3 different crews (including mine) that day prior to the mechanic's discover. I had checked the mandatory information to crew statement by the originating captain for that day, but I did not review the accompanying security paperwork for accuracy. In the future, when I am signing for an aircraft which has been flown earlier in the day, I shall include a review of the accompanying security paperwork for omissions and/or errors.
Original NASA ASRS Text
Title: AN FK100 PIC IS REMINDED BY ANOTHER CAPT THAT THE SECURITY CHK PAPERS ASSOCIATED WITH DISPATCH RELEASE ACFT NUMBERS SHOULD BE DOUBLECHKED TO VERIFY THAT THE CORRECT ACFT NOSE NUMBER IS THE SAME AT ORD, IL.
Narrative: I WAS THE CAPT OF THE REFED FLT. I RECEIVED A COURTESY CALL (VOICE MAIL) FROM ANOTHER CAPT WHO WAS SCHEDULED TO FLY THE SAME ACFT LATER THE SAME DAY. HE ADVISED ME THAT A MECH AT ORD NOTICED THAT THE SECURITY CHK PAPERWORK GENERATED BY ZZZ1 REFED NOSE NUMBER XXX INSTEAD OF YXX. THE ACFT WAS FLOWN BY 3 DIFFERENT CREWS (INCLUDING MINE) THAT DAY PRIOR TO THE MECH'S DISCOVER. I HAD CHKED THE MANDATORY INFO TO CREW STATEMENT BY THE ORIGINATING CAPT FOR THAT DAY, BUT I DID NOT REVIEW THE ACCOMPANYING SECURITY PAPERWORK FOR ACCURACY. IN THE FUTURE, WHEN I AM SIGNING FOR AN ACFT WHICH HAS BEEN FLOWN EARLIER IN THE DAY, I SHALL INCLUDE A REVIEW OF THE ACCOMPANYING SECURITY PAPERWORK FOR OMISSIONS AND/OR ERRORS.
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.