<< >> NASA ASRS Report 630254, September 2004

An A319 captain is concerned that there may be a flaw in the maintenance write-up procedure after trying to write up the aoa vane.

Attributes
ACN	630254
Time
Date	200409
Day	Fri
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : sfo.airport
State Reference	CA
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	A319
Operating Under FAR Part	Part 121
Flight Phase	ground : maintenance ground : parked
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Experience	flight time last 90 days : 140 flight time total : 12000 flight time type : 30
ASRS Report	630254
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Experience	flight time last 90 days : 24 flight time total : 7000 flight time type : 2000
ASRS Report	630257
Events
Anomaly	aircraft equipment problem : less severe maintenance problem : improper documentation non adherence : company policies
Independent Detector	other flight crewa
Consequence	other
Factors
Maintenance	performance deficiency : logbook entry
Supplementary
Problem Areas	Flight Crew Human Performance Maintenance Human Performance Company Aircraft
Primary Problem	Ambiguous

Narrative:

Upon arrival at gate in sfo, the first officer did a walkaround for the next leg. He discovered the sealant missing on an aoa (angle of attack) vane. We sent in a maintenance code, but we received an error message in response. We may have not been within the time period to send a maintenance code. No logbook, as per new procedure, so we called maintenance and gave verbal write-up. Then we learned of aircraft swap, so we went to the next airplane. How does one write up a maintenance item without a logbook or ACARS? I've been told that we cannot give verbal write-ups under any circumstances.

Related reports:

• An MD80 captain is concerned about the number of deferred it...
• CRJ200 captain is concerned when maintenance asks him to ent...

	Enter your search terms Submit search form
	Web www.37000feet.com

Original NASA ASRS Text

Title: AN A319 CAPT IS CONCERNED THAT THERE MAY BE A FLAW IN THE MAINT WRITE-UP PROC AFTER TRYING TO WRITE UP THE AOA VANE.

Narrative: UPON ARR AT GATE IN SFO, THE FO DID A WALKAROUND FOR THE NEXT LEG. HE DISCOVERED THE SEALANT MISSING ON AN AOA (ANGLE OF ATTACK) VANE. WE SENT IN A MAINT CODE, BUT WE RECEIVED AN ERROR MESSAGE IN RESPONSE. WE MAY HAVE NOT BEEN WITHIN THE TIME PERIOD TO SEND A MAINT CODE. NO LOGBOOK, AS PER NEW PROC, SO WE CALLED MAINT AND GAVE VERBAL WRITE-UP. THEN WE LEARNED OF ACFT SWAP, SO WE WENT TO THE NEXT AIRPLANE. HOW DOES ONE WRITE UP A MAINT ITEM WITHOUT A LOGBOOK OR ACARS? I'VE BEEN TOLD THAT WE CANNOT GIVE VERBAL WRITE-UPS UNDER ANY CIRCUMSTANCES.

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.