B747 crew was unable to comply with SID altitude constraints.

Attributes
ACN	433530
Time
Date	199904
Day	Mon
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : ord.airport
State Reference	IL
Altitude	msl single value : 3000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : c90.tracon
Operator	common carrier : air carrier
Make Model Name	DC-10 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Navigation In Use	other vortac
Flight Phase	climbout : initial
Route In Use	departure sid : o'hare one
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 90 flight time total : 15000 flight time type : 300
ASRS Report	433530
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : multi engine pilot : commercial pilot : instrument
Events
Anomaly	altitude deviation : crossing restriction not met non adherence : published procedure
Independent Detector	other controllera
Resolutory Action	none taken : anomaly accepted
Supplementary
Problem Areas	Flight Crew Human Performance Airspace Structure
Primary Problem	Flight Crew Human Performance

Narrative:

Flight departed late and takeoff weight was critical due to tailwinds on some runways and inadequate length on others. As we taxied out, we were assigned runway 32R, which we were not certain we could use. Crew had discussed that if our weight allowed the runway to be used, we would need to inform ATC we could not adhere to the SID crossing altitudes. We also discussed our taxi route, should our final weight not allow us to use runway 32R. As we approached the runway, we found our weight had dropped enough to use runway 32R. We were #2 for takeoff. We completed the checklist and departed. On climb out, departure asked if we were going to comply with the SID crossing altitudes. Then I remembered that we had forgot to inform ATC of this. There was no conflict. Although our workload was high, this should not have been overlooked. Next time when the issue is discussed, a call to ATC should be made at the same time.

Original NASA ASRS Text

Title: B747 CREW WAS UNABLE TO COMPLY WITH SID ALT CONSTRAINTS.

Narrative: FLT DEPARTED LATE AND TKOF WT WAS CRITICAL DUE TO TAILWINDS ON SOME RWYS AND INADEQUATE LENGTH ON OTHERS. AS WE TAXIED OUT, WE WERE ASSIGNED RWY 32R, WHICH WE WERE NOT CERTAIN WE COULD USE. CREW HAD DISCUSSED THAT IF OUR WT ALLOWED THE RWY TO BE USED, WE WOULD NEED TO INFORM ATC WE COULD NOT ADHERE TO THE SID XING ALTS. WE ALSO DISCUSSED OUR TAXI RTE, SHOULD OUR FINAL WT NOT ALLOW US TO USE RWY 32R. AS WE APCHED THE RWY, WE FOUND OUR WT HAD DROPPED ENOUGH TO USE RWY 32R. WE WERE #2 FOR TKOF. WE COMPLETED THE CHKLIST AND DEPARTED. ON CLBOUT, DEP ASKED IF WE WERE GOING TO COMPLY WITH THE SID XING ALTS. THEN I REMEMBERED THAT WE HAD FORGOT TO INFORM ATC OF THIS. THERE WAS NO CONFLICT. ALTHOUGH OUR WORKLOAD WAS HIGH, THIS SHOULD NOT HAVE BEEN OVERLOOKED. NEXT TIME WHEN THE ISSUE IS DISCUSSED, A CALL TO ATC SHOULD BE MADE AT THE SAME TIME.

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.