An airbus 320 was dispatched in non compliance with an open log item entered in ACARS but with no lo...

Attributes
ACN	437040
Time
Date	199905
Day	Wed
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : zzz.airport
State Reference	US
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	A320
Operating Under FAR Part	Part 121
Flight Phase	ground : maintenance ground : parked ground : preflight
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	maintenance : technician
Qualification	technician : powerplant technician : airframe
ASRS Report	437040
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	aircraft equipment problem : less severe maintenance problem : improper documentation non adherence : published procedure
Resolutory Action	none taken : detected after the fact
Consequence	other
Factors
Maintenance	performance deficiency : logbook entry performance deficiency : non compliance with legal requirements
Supplementary
Problem Areas	Company Flight Crew Human Performance Maintenance Human Performance
Primary Problem	Flight Crew Human Performance

Narrative:

An open log write-up not put in the logbook, but sent via ACARS. After aircraft departed station, a maintenance alert was sent to maintenance stating there were open log reports. Corrective action: require crews to make write-ups in logbook, not just in ACARS. Because I felt that I had checked for open log reports and did not see any, I felt that no further action was required per air carrier volume 1, book 1. After the aircraft arrived, I checked the logbook and again did not find any open log reports, and again because air carrier volume 1, book 1 states that if there is no maintenance required, the current release is good, so I did not release the aircraft which would have also showed the logs.

Original NASA ASRS Text

Title: AN AIRBUS 320 WAS DISPATCHED IN NON COMPLIANCE WITH AN OPEN LOG ITEM ENTERED IN ACARS BUT WITH NO LOGBOOK ENTRY.

Narrative: AN OPEN LOG WRITE-UP NOT PUT IN THE LOGBOOK, BUT SENT VIA ACARS. AFTER ACFT DEPARTED STATION, A MAINT ALERT WAS SENT TO MAINT STATING THERE WERE OPEN LOG RPTS. CORRECTIVE ACTION: REQUIRE CREWS TO MAKE WRITE-UPS IN LOGBOOK, NOT JUST IN ACARS. BECAUSE I FELT THAT I HAD CHKED FOR OPEN LOG RPTS AND DID NOT SEE ANY, I FELT THAT NO FURTHER ACTION WAS REQUIRED PER ACR VOLUME 1, BOOK 1. AFTER THE ACFT ARRIVED, I CHKED THE LOGBOOK AND AGAIN DID NOT FIND ANY OPEN LOG RPTS, AND AGAIN BECAUSE ACR VOLUME 1, BOOK 1 STATES THAT IF THERE IS NO MAINT REQUIRED, THE CURRENT RELEASE IS GOOD, SO I DID NOT RELEASE THE ACFT WHICH WOULD HAVE ALSO SHOWED THE LOGS.

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.

An airbus 320 was dispatched in non compliance with an open log item entered in ACARS but with no logbook entry.