An md super 80 was dispatched in non compliance with the logbook not boarded.

Attributes
ACN	433850
Time
Date	199904
Day	Sun
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : tus.airport
State Reference	AZ
Altitude	agl single value : 0
Environment
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	MD-80 Super 80
Operating Under FAR Part	Part 121
Flight Phase	ground : parked ground : preflight
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
ASRS Report	433850
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : commercial pilot : instrument pilot : multi engine
Events
Anomaly	aircraft equipment problem : less severe non adherence : far non adherence : published procedure non adherence other
Independent Detector	other other : cgp 4
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:

Arrival at tus airport at BA45 local. Monitors and gate agents have us departing gate zy. I load my kit bag and suitcase onto aircraft at gate zy. I move a logbook resting on the captain's seat to the glareshield. At about the same time, the first class flight attendant tells me that we are catered for dfw not ord. I check with the agent. He said we've got to move aircraft and reload at gate zx. Still no flight plan BA25. At BA30 I enter the cockpit with flight plan. We run checklists and depart on schedule. At approximately BA48Z we receive an ACARS message informing us of the logbook problem. We search the cockpit, can't find it. We answer the message and call dispatch and maintenance technician to confirm that the flight plan remarks section agrees with their records. No MEL/pdl/AC items. Maintenance tells us to expect a temporary logbook at the gate at ord. The temporary logbook is delivered to the aircraft. Contributing factors: change of gates/aircraft. But the bottom line is -- we left our logbook at tucson.

Original NASA ASRS Text

Title: AN MD SUPER 80 WAS DISPATCHED IN NON COMPLIANCE WITH THE LOGBOOK NOT BOARDED.

Narrative: ARR AT TUS ARPT AT BA45 LCL. MONITORS AND GATE AGENTS HAVE US DEPARTING GATE ZY. I LOAD MY KIT BAG AND SUITCASE ONTO ACFT AT GATE ZY. I MOVE A LOGBOOK RESTING ON THE CAPT'S SEAT TO THE GLARESHIELD. AT ABOUT THE SAME TIME, THE FIRST CLASS FLT ATTENDANT TELLS ME THAT WE ARE CATERED FOR DFW NOT ORD. I CHK WITH THE AGENT. HE SAID WE'VE GOT TO MOVE ACFT AND RELOAD AT GATE ZX. STILL NO FLT PLAN BA25. AT BA30 I ENTER THE COCKPIT WITH FLT PLAN. WE RUN CHKLISTS AND DEPART ON SCHEDULE. AT APPROX BA48Z WE RECEIVE AN ACARS MESSAGE INFORMING US OF THE LOGBOOK PROB. WE SEARCH THE COCKPIT, CAN'T FIND IT. WE ANSWER THE MESSAGE AND CALL DISPATCH AND MAINT TECHNICIAN TO CONFIRM THAT THE FLT PLAN REMARKS SECTION AGREES WITH THEIR RECORDS. NO MEL/PDL/AC ITEMS. MAINT TELLS US TO EXPECT A TEMPORARY LOGBOOK AT THE GATE AT ORD. THE TEMPORARY LOGBOOK IS DELIVERED TO THE ACFT. CONTRIBUTING FACTORS: CHANGE OF GATES/ACFT. BUT THE BOTTOM LINE IS -- WE LEFT OUR LOGBOOK AT TUCSON.

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.