37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 373272 |
Time | |
Date | 199707 |
Day | Mon |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : cmh |
State Reference | OH |
Altitude | agl bound lower : 0 agl bound upper : 0 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | A320 |
Operating Under FAR Part | Part 121 |
Navigation In Use | Other Other |
Flight Phase | ground : parked ground : preflight |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Experience | flight time last 90 days : 200 flight time total : 10000 flight time type : 600 |
ASRS Report | 373272 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : instrument pilot : atp pilot : commercial |
Experience | flight time last 90 days : 100 flight time total : 7700 flight time type : 100 |
ASRS Report | 375220 |
Events | |
Anomaly | aircraft equipment problem : less severe non adherence : far non adherence other other anomaly other |
Independent Detector | other flight crewa |
Resolutory Action | none taken : detected after the fact |
Consequence | Other |
Supplementary | |
Primary Problem | Aircraft |
Air Traffic Incident | Pilot Deviation other |
Narrative:
Prior to pushback for a flight from cmh to ewr, technicians were in the cockpit and blocked our access until about 15-20 mins prior to departure. Once in the cockpit, I reviewed the newly added MEL, noted that we would need to add it to our release, and called maintenance back out as the placard they installed was not worded correctly. We continued our preflight preparations, maintenance came and corrected the placard and left again. Almost immediately, we had another computer fault and had to call maintenance again. During all this we were also working on obtaining correct takeoff runway data as cmh had a shortened runway. One of the entry door slides would not arm properly and all this was distracting. The MEL requested certain actions prior to departure and a logbook entry which we complied with but with all the distrs, I forgot to contact dispatch to get the MEL added to our release. We discovered this en route to ewr. This type of mass distraction just prior to pushback is common. I try harder than anyone to make sure we are safe and legal, but occasionally anyone can make this kind of mistake. The daily legal ramifications of compliance with fom, FARS, MEL, etc, are numerous and serious. In fact, an argument could be made that with so many legal technicalities to consider, a pilot's time to properly consider the real safety factors is reduced. I would advocate some type of a legalities checklist to help remind us of those requirements. Let's face it -- the regulations are increasing by number and complexity every yr. This problem will only get worse. Is there a way for pilots to stay absolutely legal on every flight? My only idea is to require an additional checklist or require verbal dispatch contact prior to every flight for review of aircraft status, WX etc.
Original NASA ASRS Text
Title: AN A320 CREW FAIL TO ADD THE MEL TO THEIR FLT RELEASE. HAD FAILED TO CONTACT DISPATCH AS THEY WERE TASK SATURATED AT THE RAMP PRIOR TO DEP TIME. PIC SAYS IT OCCURS ALL THE TIME.
Narrative: PRIOR TO PUSHBACK FOR A FLT FROM CMH TO EWR, TECHNICIANS WERE IN THE COCKPIT AND BLOCKED OUR ACCESS UNTIL ABOUT 15-20 MINS PRIOR TO DEP. ONCE IN THE COCKPIT, I REVIEWED THE NEWLY ADDED MEL, NOTED THAT WE WOULD NEED TO ADD IT TO OUR RELEASE, AND CALLED MAINT BACK OUT AS THE PLACARD THEY INSTALLED WAS NOT WORDED CORRECTLY. WE CONTINUED OUR PREFLT PREPARATIONS, MAINT CAME AND CORRECTED THE PLACARD AND LEFT AGAIN. ALMOST IMMEDIATELY, WE HAD ANOTHER COMPUTER FAULT AND HAD TO CALL MAINT AGAIN. DURING ALL THIS WE WERE ALSO WORKING ON OBTAINING CORRECT TKOF RWY DATA AS CMH HAD A SHORTENED RWY. ONE OF THE ENTRY DOOR SLIDES WOULD NOT ARM PROPERLY AND ALL THIS WAS DISTRACTING. THE MEL REQUESTED CERTAIN ACTIONS PRIOR TO DEP AND A LOGBOOK ENTRY WHICH WE COMPLIED WITH BUT WITH ALL THE DISTRS, I FORGOT TO CONTACT DISPATCH TO GET THE MEL ADDED TO OUR RELEASE. WE DISCOVERED THIS ENRTE TO EWR. THIS TYPE OF MASS DISTR JUST PRIOR TO PUSHBACK IS COMMON. I TRY HARDER THAN ANYONE TO MAKE SURE WE ARE SAFE AND LEGAL, BUT OCCASIONALLY ANYONE CAN MAKE THIS KIND OF MISTAKE. THE DAILY LEGAL RAMIFICATIONS OF COMPLIANCE WITH FOM, FARS, MEL, ETC, ARE NUMEROUS AND SERIOUS. IN FACT, AN ARGUMENT COULD BE MADE THAT WITH SO MANY LEGAL TECHNICALITIES TO CONSIDER, A PLT'S TIME TO PROPERLY CONSIDER THE REAL SAFETY FACTORS IS REDUCED. I WOULD ADVOCATE SOME TYPE OF A LEGALITIES CHKLIST TO HELP REMIND US OF THOSE REQUIREMENTS. LET'S FACE IT -- THE REGS ARE INCREASING BY NUMBER AND COMPLEXITY EVERY YR. THIS PROB WILL ONLY GET WORSE. IS THERE A WAY FOR PLTS TO STAY ABSOLUTELY LEGAL ON EVERY FLT? MY ONLY IDEA IS TO REQUIRE AN ADDITIONAL CHKLIST OR REQUIRE VERBAL DISPATCH CONTACT PRIOR TO EVERY FLT FOR REVIEW OF ACFT STATUS, WX ETC.
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.