MD83 crew leaves pdx without logbook.

Attributes
ACN	437780
Time
Date	199905
Day	Fri
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : pdx.airport
State Reference	OR
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	MD-83
Operating Under FAR Part	Part 121
Flight Phase	ground : parked
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : cfi pilot : atp pilot : flight engineer
Experience	flight time last 90 days : 180 flight time total : 15500 flight time type : 7000
ASRS Report	437780
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : cfi pilot : atp pilot : flight engineer
Experience	flight time last 90 days : 180 flight time total : 5100 flight time type : 300
ASRS Report	437863
Events
Anomaly	aircraft equipment problem : less severe maintenance problem : improper documentation non adherence : far
Independent Detector	other flight crewa other flight crewb
Resolutory Action	none taken : detected after the fact
Consequence	other
Supplementary
Problem Areas	Flight Crew Human Performance Maintenance Human Performance
Primary Problem	Flight Crew Human Performance

Narrative:

Noticed that the aircraft logbook was missing. This was a through flight and there was no indication of any problems with inbound flight. The first officer and captain began preflight duties and then captain went to retrieve flight paperwork in terminal gate area. Captain signed paperwork, confirmed fuel load and observed MEL's that may affect performance data. 15 mins prior to departure captain returns to aircraft and first officer and captain review MEL's and determine that normal takeoff and landing data cards cannot be used and that our takeoff data must be taken from expanded performance book. We ran through our before start checklist and feel that we became distraction by MEL's performance concerns during that checklist and over looked the fact that the aircraft logbook was still not on aircraft. We departed pdx without logbook. We found that there were no open items in said logbook and no real explanation why book was taken off and not returned prior to departure. 1) first officer or captain should have called maintenance immediately as to missing logbook. 2) first officer and/or captain should have done something in cockpit to remind us that something was not complete, ie, note on yoke, etc.

Original NASA ASRS Text

Title: MD83 CREW LEAVES PDX WITHOUT LOGBOOK.

Narrative: NOTICED THAT THE ACFT LOGBOOK WAS MISSING. THIS WAS A THROUGH FLT AND THERE WAS NO INDICATION OF ANY PROBS WITH INBOUND FLT. THE FO AND CAPT BEGAN PREFLT DUTIES AND THEN CAPT WENT TO RETRIEVE FLT PAPERWORK IN TERMINAL GATE AREA. CAPT SIGNED PAPERWORK, CONFIRMED FUEL LOAD AND OBSERVED MEL'S THAT MAY AFFECT PERFORMANCE DATA. 15 MINS PRIOR TO DEP CAPT RETURNS TO ACFT AND FO AND CAPT REVIEW MEL'S AND DETERMINE THAT NORMAL TKOF AND LNDG DATA CARDS CANNOT BE USED AND THAT OUR TKOF DATA MUST BE TAKEN FROM EXPANDED PERFORMANCE BOOK. WE RAN THROUGH OUR BEFORE START CHKLIST AND FEEL THAT WE BECAME DISTR BY MEL'S PERFORMANCE CONCERNS DURING THAT CHKLIST AND OVER LOOKED THE FACT THAT THE ACFT LOGBOOK WAS STILL NOT ON ACFT. WE DEPARTED PDX WITHOUT LOGBOOK. WE FOUND THAT THERE WERE NO OPEN ITEMS IN SAID LOGBOOK AND NO REAL EXPLANATION WHY BOOK WAS TAKEN OFF AND NOT RETURNED PRIOR TO DEP. 1) FO OR CAPT SHOULD HAVE CALLED MAINT IMMEDIATELY AS TO MISSING LOGBOOK. 2) FO AND/OR CAPT SHOULD HAVE DONE SOMETHING IN COCKPIT TO REMIND US THAT SOMETHING WAS NOT COMPLETE, IE, NOTE ON YOKE, 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.