Flight crew of B737-300 depart bos without obtaining final weight and balance data.

Attributes
ACN	610679
Time
Date	200403
Day	Tue
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : bos.airport
State Reference	MA
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : bos.tower
Operator	common carrier : air carrier
Make Model Name	B737-300
Operating Under FAR Part	Part 121
Flight Phase	climbout : takeoff ground : parked ground : preflight ground : takeoff roll
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : commercial pilot : flight engineer pilot : atp pilot : instrument pilot : multi engine
Experience	flight time last 90 days : 150 flight time total : 20000 flight time type : 12000
ASRS Report	610679
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Events
Anomaly	non adherence : far non adherence : published procedure non adherence : company policies
Independent Detector	other flight crewa
Resolutory Action	none taken : detected after the fact
Supplementary
Problem Areas	Airport Company Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance

Narrative:

Before takeoff checklist completed to the line. Approaching hold short line, tower offered immediate takeoff clearance (traffic on 2 mi final). Accepted immediate takeoff clearance. Continued roll into takeoff position, before takeoff checklist completed below the line. Conducted normal takeoff and departure. Flight inadvertently departed without obtaining final weight/balance data. Relative factor: the major cause of this error was rushing. Contributing factors: 1) setting the takeoff and performance data at the gate utilizing tps. 2) close proximity of gate and runway and lack of ground traffic. 3) acceptance of immediate takeoff clearance without thoroughly reviewing all required data. 4) not ensuring that all weight/balance data received prior to departure. Corrective actions: 1) don't rush. 2) thoroughly review all pre-takeoff data. 3) ensure that all weight and balance data has been received prior to departure.

Original NASA ASRS Text

Title: FLT CREW OF B737-300 DEPART BOS WITHOUT OBTAINING FINAL WT AND BAL DATA.

Narrative: BEFORE TKOF CHKLIST COMPLETED TO THE LINE. APCHING HOLD SHORT LINE, TWR OFFERED IMMEDIATE TKOF CLRNC (TFC ON 2 MI FINAL). ACCEPTED IMMEDIATE TKOF CLRNC. CONTINUED ROLL INTO TKOF POS, BEFORE TKOF CHKLIST COMPLETED BELOW THE LINE. CONDUCTED NORMAL TKOF AND DEP. FLT INADVERTENTLY DEPARTED WITHOUT OBTAINING FINAL WT/BAL DATA. RELATIVE FACTOR: THE MAJOR CAUSE OF THIS ERROR WAS RUSHING. CONTRIBUTING FACTORS: 1) SETTING THE TKOF AND PERFORMANCE DATA AT THE GATE UTILIZING TPS. 2) CLOSE PROX OF GATE AND RWY AND LACK OF GND TFC. 3) ACCEPTANCE OF IMMEDIATE TKOF CLRNC WITHOUT THOROUGHLY REVIEWING ALL REQUIRED DATA. 4) NOT ENSURING THAT ALL WT/BAL DATA RECEIVED PRIOR TO DEP. CORRECTIVE ACTIONS: 1) DON'T RUSH. 2) THOROUGHLY REVIEW ALL PRE-TKOF DATA. 3) ENSURE THAT ALL WT AND BAL DATA HAS BEEN RECEIVED PRIOR TO DEP.

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.