37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 716122 |
Time | |
Date | 200611 |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : zzz.airport |
State Reference | US |
Altitude | msl single value : 15000 |
Environment | |
Flight Conditions | IMC |
Aircraft 1 | |
Controlling Facilities | artcc : zzz.artcc tracon : zzz.tracon tower : zzz.tower tower : zzz.tower |
Operator | common carrier : air carrier |
Make Model Name | A320 |
Operating Under FAR Part | Part 121 |
Flight Phase | climbout : initial |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Experience | flight time last 90 days : 200 flight time total : 9000 flight time type : 350 |
ASRS Report | 716122 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Experience | flight time last 90 days : 90 flight time total : 23000 flight time type : 3000 |
ASRS Report | 716123 |
Events | |
Anomaly | aircraft equipment problem : less severe maintenance problem : improper documentation maintenance problem : improper maintenance non adherence : published procedure non adherence : company policies non adherence : far |
Independent Detector | other other : 3 |
Resolutory Action | none taken : detected after the fact |
Consequence | other |
Supplementary | |
Problem Areas | Maintenance Human Performance Aircraft Company |
Primary Problem | Ambiguous |
Narrative:
We picked up a new aircraft in ZZZ. We were told by the inbound crew that there were a couple of write-ups. We also noticed a maintenance message and sent in another write-up. There was a mechanic on board while doing this and he said he would address all the write-ups by deferring them; then send us a new mrd. We received the mrd prior to push and it had all the items we had discussed deferred. We then taxied out and departed iad. On climb out we received 2 ACARS messages; both of which were log items we had addressed on the ground and were already deferred on our mrd. I thought that this was odd to be receiving these at this time so I requested a verification of the current mrd and release. It came back with the correct current release and 'mrd no.' we then contacted maintenance and asked if they had any idea what was going on. They said that our mrd was invalid. We asked how this could have happened and maintenance said that ACARS had gone down for a while. We said that we had been sent an mrd on the ground in ZZZ; before push; that addressed all our write-ups in ZZZ along with current MEL's and all the correct deferral stickers were in place. The mechanic referenced the ACARS outage as the probable misconnect and it would be resolved in ZZZ1.
Original NASA ASRS Text
Title: AN A320 CREW DEPARTED WITH OPEN MAINT ITEMS FOLLOWING AN ACARS OUTAGE THAT PREVENTED RECEIPT OF THE APPROPRIATE DEFERRAL OF OPEN ITEMS.
Narrative: WE PICKED UP A NEW ACFT IN ZZZ. WE WERE TOLD BY THE INBOUND CREW THAT THERE WERE A COUPLE OF WRITE-UPS. WE ALSO NOTICED A MAINT MESSAGE AND SENT IN ANOTHER WRITE-UP. THERE WAS A MECH ON BOARD WHILE DOING THIS AND HE SAID HE WOULD ADDRESS ALL THE WRITE-UPS BY DEFERRING THEM; THEN SEND US A NEW MRD. WE RECEIVED THE MRD PRIOR TO PUSH AND IT HAD ALL THE ITEMS WE HAD DISCUSSED DEFERRED. WE THEN TAXIED OUT AND DEPARTED IAD. ON CLBOUT WE RECEIVED 2 ACARS MESSAGES; BOTH OF WHICH WERE LOG ITEMS WE HAD ADDRESSED ON THE GND AND WERE ALREADY DEFERRED ON OUR MRD. I THOUGHT THAT THIS WAS ODD TO BE RECEIVING THESE AT THIS TIME SO I REQUESTED A VERIFICATION OF THE CURRENT MRD AND RELEASE. IT CAME BACK WITH THE CORRECT CURRENT RELEASE AND 'MRD NO.' WE THEN CONTACTED MAINT AND ASKED IF THEY HAD ANY IDEA WHAT WAS GOING ON. THEY SAID THAT OUR MRD WAS INVALID. WE ASKED HOW THIS COULD HAVE HAPPENED AND MAINT SAID THAT ACARS HAD GONE DOWN FOR A WHILE. WE SAID THAT WE HAD BEEN SENT AN MRD ON THE GND IN ZZZ; BEFORE PUSH; THAT ADDRESSED ALL OUR WRITE-UPS IN ZZZ ALONG WITH CURRENT MEL'S AND ALL THE CORRECT DEFERRAL STICKERS WERE IN PLACE. THE MECH REFED THE ACARS OUTAGE AS THE PROBABLE MISCONNECT AND IT WOULD BE RESOLVED IN ZZZ1.
Data retrieved from NASA's ASRS site as of January 2009 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.