 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
An A319 captain admitted that he departed iad with a known brake problem when he should have taxied back to have the item taken care of by maintenance before departure.
| Attributes | |
| ACN | 629130 |
| Time | |
| Date | 200408 |
| Day | Sun |
| Local Time Of Day | 1801 To 2400 |
| Place | |
| Locale Reference | airport : iad.airport |
| State Reference | DC |
| Altitude | agl single value : 0 |
| Environment | |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tower : dfw.tower |
| Operator | common carrier : air carrier |
| Make Model Name | A319 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | ground : taxi ground : parked |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| ASRS Report | 629130 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Events | |
| Anomaly | aircraft equipment problem : less severe maintenance problem : improper documentation non adherence : company policies non adherence : far non adherence : published procedure |
| Independent Detector | aircraft equipment other aircraft equipment : ecam other flight crewa other flight crewb |
| Resolutory Action | none taken : detected after the fact |
| Consequence | other |
| Supplementary | |
| Problem Areas | Aircraft Flight Crew Human Performance |
| Primary Problem | Flight Crew Human Performance |
Narrative:
I accepted an aircraft in iad for a flight to ZZZ. After getting the aircraft at the gate, the APU failed. We accomplished the MEL procedures for the item. We taxied late and were given a circuitous route to the taxiway, with numerous delays. Upon arrival at the end of the runway holding for takeoff, we had an ECAM message for a bscu #2 fault. I mistakenly idented it as a class ii fault and looked up in the MEL, that states after push, you can go if it can be dispatched under the MEL. It was, and we departed. After takeoff, we reviewed the item again and I determined that it was a class I message that needed to be written up and taken care of by maintenance prior to takeoff. Upon arrival in ZZZ, the item was written up, and maintenance reset the system and no fault was found. The fom states all maintenance items will be written up, while the MEL states that you can go with a class ii after push. This is a problem that needs to be corrected. I am now fully aware of the differences between class I and ii. It won't happen again.
Original NASA ASRS Text
Title: AN A319 CAPT ADMITTED THAT HE DEPARTED IAD WITH A KNOWN BRAKE PROB WHEN HE SHOULD HAVE TAXIED BACK TO HAVE THE ITEM TAKEN CARE OF BY MAINT BEFORE DEP.
Narrative: I ACCEPTED AN ACFT IN IAD FOR A FLT TO ZZZ. AFTER GETTING THE ACFT AT THE GATE, THE APU FAILED. WE ACCOMPLISHED THE MEL PROCS FOR THE ITEM. WE TAXIED LATE AND WERE GIVEN A CIRCUITOUS RTE TO THE TXWY, WITH NUMEROUS DELAYS. UPON ARRIVAL AT THE END OF THE RWY HOLDING FOR TKOF, WE HAD AN ECAM MESSAGE FOR A BSCU #2 FAULT. I MISTAKENLY IDENTED IT AS A CLASS II FAULT AND LOOKED UP IN THE MEL, THAT STATES AFTER PUSH, YOU CAN GO IF IT CAN BE DISPATCHED UNDER THE MEL. IT WAS, AND WE DEPARTED. AFTER TKOF, WE REVIEWED THE ITEM AGAIN AND I DETERMINED THAT IT WAS A CLASS I MESSAGE THAT NEEDED TO BE WRITTEN UP AND TAKEN CARE OF BY MAINT PRIOR TO TKOF. UPON ARR IN ZZZ, THE ITEM WAS WRITTEN UP, AND MAINT RESET THE SYS AND NO FAULT WAS FOUND. THE FOM STATES ALL MAINT ITEMS WILL BE WRITTEN UP, WHILE THE MEL STATES THAT YOU CAN GO WITH A CLASS II AFTER PUSH. THIS IS A PROB THAT NEEDS TO BE CORRECTED. I AM NOW FULLY AWARE OF THE DIFFERENCES BTWN CLASS I AND II. IT WON'T HAPPEN AGAIN.
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.