 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
PIC of B737 freighter fails to change flight plan coding so as to reflect the correct status relative to CAT ii operations. The logbook carried some aircraft equipment problems or deferments that disallowed any CAT ii type operations.
| Attributes | |
| ACN | 370830 |
| Time | |
| Date | 199706 |
| Day | Fri |
| Local Time Of Day | 1801 To 2400 |
| Place | |
| Locale Reference | airport : lbb |
| State Reference | TX |
| Altitude | agl bound lower : 0 agl bound upper : 0 |
| Environment | |
| Flight Conditions | VMC |
| Light | Night |
| Aircraft 1 | |
| Controlling Facilities | tower : las |
| Operator | common carrier : air carrier |
| Make Model Name | B727-200 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | ground : preflight |
| Flight Plan | None |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : flight engineer pilot : commercial pilot : cfi pilot : atp |
| Experience | flight time last 90 days : 100 flight time total : 7000 flight time type : 200 |
| ASRS Report | 370830 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : commercial pilot : instrument |
| Events | |
| Anomaly | aircraft equipment problem : less severe non adherence : far non adherence : published procedure 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:
Flight plan release reflected aircraft to be in CAT ii status. However, during our layover, I noticed that the maintenance at lubbock station had worked on aircraft and the logbook (and airplane) was in 'not CAT ii' status. I did not update flight plan/release to reflect it. We operated flight under IFR flight plan, and visual (VFR) conditions existed at our destination. I am simply concerned that the paperwork between the flight plan/release and the aircraft log did not agree. Flight was normal with no incidents.
Original NASA ASRS Text
Title: PIC OF B737 FREIGHTER FAILS TO CHANGE FLT PLAN CODING SO AS TO REFLECT THE CORRECT STATUS RELATIVE TO CAT II OPS. THE LOGBOOK CARRIED SOME ACFT EQUIP PROBS OR DEFERMENTS THAT DISALLOWED ANY CAT II TYPE OPS.
Narrative: FLT PLAN RELEASE REFLECTED ACFT TO BE IN CAT II STATUS. HOWEVER, DURING OUR LAYOVER, I NOTICED THAT THE MAINT AT LUBBOCK STATION HAD WORKED ON ACFT AND THE LOGBOOK (AND AIRPLANE) WAS IN 'NOT CAT II' STATUS. I DID NOT UPDATE FLT PLAN/RELEASE TO REFLECT IT. WE OPERATED FLT UNDER IFR FLT PLAN, AND VISUAL (VFR) CONDITIONS EXISTED AT OUR DEST. I AM SIMPLY CONCERNED THAT THE PAPERWORK BTWN THE FLT PLAN/RELEASE AND THE ACFT LOG DID NOT AGREE. FLT WAS NORMAL WITH NO INCIDENTS.
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.