 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Air carrier PIC report related to a maintenance release and its valid period. Reporter uncertain as to the legality of the verbal explanation regarding the time for release to expire.
| Attributes | |
| ACN | 351430 |
| Time | |
| Date | 199610 |
| Day | Sat |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | airport : slc |
| State Reference | UT |
| Altitude | agl bound lower : 0 agl bound upper : 0 |
| Environment | |
| Flight Conditions | Mixed |
| Light | Daylight |
| Aircraft 1 | |
| Operator | common carrier : air carrier |
| Make Model Name | Commercial Fixed Wing |
| Operating Under FAR Part | Part 121 |
| Flight Phase | ground : preflight |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp pilot : instrument pilot : flight engineer pilot : commercial |
| Experience | flight time last 90 days : 200 flight time total : 10000 flight time type : 300 |
| ASRS Report | 351430 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : instrument pilot : commercial |
| Events | |
| Anomaly | aircraft equipment problem : less severe non adherence : published procedure non adherence : far non adherence other other anomaly other |
| Independent Detector | other flight crewa |
| Resolutory Action | none taken : anomaly accepted |
| Consequence | Other |
| Supplementary | |
| Primary Problem | Aircraft |
| Air Traffic Incident | Pilot Deviation other |
Narrative:
FAA approved flight operations manual requires a current maintenance release for the aircraft being flown. The release is good for 3 universal time clock (UTC) calendar days. The logbook showed a maintenance release signed off on oct/ab/96 (local). That means the release would expire at the end of oct/ad/96 (UTC). A call to maintenance control, however, determined that, although the release was signed off on the oct/ab/96 it was signed off for oct/AC/96 (UTC). That meant the release was good through the end of the day oct/ae/96 (UTC). Since maintenance personnel are responsible for tracking the release and its currency (per our flight operations manual) I assumed per this phone conversation that the release on my aircraft was good and flew the flight from slc to msp. My question is with no written proof of this conversation and nothing in the logbook to back me up on the validity/currency of the release, how could I prove to the FAA that I was legal is accepting this aircraft?
Original NASA ASRS Text
Title: ACR PIC RPT RELATED TO A MAINT RELEASE AND ITS VALID PERIOD. RPTR UNCERTAIN AS TO THE LEGALITY OF THE VERBAL EXPLANATION REGARDING THE TIME FOR RELEASE TO EXPIRE.
Narrative: FAA APPROVED FLT OPS MANUAL REQUIRES A CURRENT MAINT RELEASE FOR THE ACFT BEING FLOWN. THE RELEASE IS GOOD FOR 3 UNIVERSAL TIME CLOCK (UTC) CALENDAR DAYS. THE LOGBOOK SHOWED A MAINT RELEASE SIGNED OFF ON OCT/AB/96 (LCL). THAT MEANS THE RELEASE WOULD EXPIRE AT THE END OF OCT/AD/96 (UTC). A CALL TO MAINT CTL, HOWEVER, DETERMINED THAT, ALTHOUGH THE RELEASE WAS SIGNED OFF ON THE OCT/AB/96 IT WAS SIGNED OFF FOR OCT/AC/96 (UTC). THAT MEANT THE RELEASE WAS GOOD THROUGH THE END OF THE DAY OCT/AE/96 (UTC). SINCE MAINT PERSONNEL ARE RESPONSIBLE FOR TRACKING THE RELEASE AND ITS CURRENCY (PER OUR FLT OPS MANUAL) I ASSUMED PER THIS PHONE CONVERSATION THAT THE RELEASE ON MY ACFT WAS GOOD AND FLEW THE FLT FROM SLC TO MSP. MY QUESTION IS WITH NO WRITTEN PROOF OF THIS CONVERSATION AND NOTHING IN THE LOGBOOK TO BACK ME UP ON THE VALIDITY/CURRENCY OF THE RELEASE, HOW COULD I PROVE TO THE FAA THAT I WAS LEGAL IS ACCEPTING THIS ACFT?
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.