Fatigued flight crew of a B737-300 leaves logbook in bos.

Attributes
ACN	453010
Time
Date	199910
Day	Tue
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : bos.airport
State Reference	MA
Altitude	agl single value : 66 msl single value : 22000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zbw.artcc
Operator	common carrier : air carrier
Make Model Name	B737-300
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	climbout : intermediate altitude climbout : vacating altitude
Route In Use	departure : other published ifr departure
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp pilot : flight engineer pilot : multi engine
Experience	flight time last 90 days : 180 flight time total : 13000 flight time type : 80
ASRS Report	453010
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 maintenance problem : improper documentation non adherence : far
Independent Detector	other flight crewa other flight crewb
Resolutory Action	none taken : anomaly accepted
Consequence	other
Supplementary
Problem Areas	Maintenance Human Performance Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Departing bos at XA56 local, climbing through FL220 after departing bos, realized we had taken off without the logbook. We had had an 'early' morning departure out of phl. This was the 4TH day of a 5 day stretch of trips. We changed planes in bos. Getting the aircraft ready and doing the cockpit preparation, I noticed the logbook was missing and made a mental note to call operations. During the next several mins, several distractions came up, including a discrepancy in passenger count. Trying to find the right fom page to verify the actions and doing checklist and getting the agent to verify the ticket count, the logbook issue disappeared. Climbing through FL220, it occurred to me I had not signed the logbook and found it was not onboard. Everything comes back to communication and taking one thing at a time. I should have said something to the first officer that we needed to call maintenance and check on the logbook -- made a written note and performed one thing at a time rather than trying to do several things once.

Original NASA ASRS Text

Title: FATIGUED FLC OF A B737-300 LEAVES LOGBOOK IN BOS.

Narrative: DEPARTING BOS AT XA56 LCL, CLBING THROUGH FL220 AFTER DEPARTING BOS, REALIZED WE HAD TAKEN OFF WITHOUT THE LOGBOOK. WE HAD HAD AN 'EARLY' MORNING DEP OUT OF PHL. THIS WAS THE 4TH DAY OF A 5 DAY STRETCH OF TRIPS. WE CHANGED PLANES IN BOS. GETTING THE ACFT READY AND DOING THE COCKPIT PREPARATION, I NOTICED THE LOGBOOK WAS MISSING AND MADE A MENTAL NOTE TO CALL OPS. DURING THE NEXT SEVERAL MINS, SEVERAL DISTRACTIONS CAME UP, INCLUDING A DISCREPANCY IN PAX COUNT. TRYING TO FIND THE RIGHT FOM PAGE TO VERIFY THE ACTIONS AND DOING CHKLIST AND GETTING THE AGENT TO VERIFY THE TICKET COUNT, THE LOGBOOK ISSUE DISAPPEARED. CLBING THROUGH FL220, IT OCCURRED TO ME I HAD NOT SIGNED THE LOGBOOK AND FOUND IT WAS NOT ONBOARD. EVERYTHING COMES BACK TO COM AND TAKING ONE THING AT A TIME. I SHOULD HAVE SAID SOMETHING TO THE FO THAT WE NEEDED TO CALL MAINT AND CHK ON THE LOGBOOK -- MADE A WRITTEN NOTE AND PERFORMED ONE THING AT A TIME RATHER THAN TRYING TO DO SEVERAL THINGS ONCE.

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.