37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1726907 |
Time | |
Date | 202002 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ORD.Airport |
State Reference | IL |
Environment | |
Flight Conditions | VMC |
Aircraft 1 | |
Make Model Name | Large Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Climb |
Route In Use | SID ORD5 |
Flight Plan | IFR |
Person 1 | |
Function | First Officer Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Instrument Flight Crew Multiengine |
Experience | Flight Crew Total 4500 |
Person 2 | |
Function | Captain Pilot Not Flying |
Qualification | Flight Crew Multiengine Flight Crew Instrument Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Total 17500 |
Events | |
Anomaly | Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Speed All Types |
Narrative:
On departure from ord runway 22L; (ORD5 departure); crew were given 180 heading and complied with this direction after takeoff. Shortly thereafter determined we would not achieve published climb gradient and pm (pilot monitoring) immediately notified ATC. ATC then informed crew of possible conflict; but did not assign different heading or altitude.turning south off runway 22L shortens the distance available to achieve climb gradients on this radar SID with a problematic lack of information (specifically track distance) to determine climb performance. Additionally; with the heading being assigned as the aircraft is cleared for takeoff this provides little time to assess performance. There appears to be a lack of pre-charted information with wat (weight; altitude; temperature) inputs to assist in rapid climb assessment.publish a wat (weight; altitude; temperature) based chart for aircraft based on a worst case track distance off selected runways at ord for specific runways...basically a regulated takeoff graph (rtog). Suggest ord implement more RNAV sids...track distance on established procedures is key. Crews may want to consider requesting headings other than 180 on the ORD5 as well; or request other departure runways with more frequency.
Original NASA ASRS Text
Title: Air carrier flight crew discovered during initial climbout from ORD that they were unable to meet the climb gradient requirement for the ORD5 Departure.
Narrative: On departure from ORD Runway 22L; (ORD5 Departure); crew were given 180 heading and complied with this direction after takeoff. Shortly thereafter determined we would not achieve published climb gradient and PM (Pilot Monitoring) immediately notified ATC. ATC then informed crew of possible conflict; but did not assign different heading or altitude.Turning south off Runway 22L shortens the distance available to achieve climb gradients on this radar SID with a problematic lack of information (specifically track distance) to determine climb performance. Additionally; with the heading being assigned as the aircraft is cleared for takeoff this provides little time to assess performance. There appears to be a lack of pre-charted information with WAT (Weight; Altitude; Temperature) inputs to assist in rapid climb assessment.Publish a WAT (Weight; Altitude; Temperature) based chart for aircraft based on a worst case track distance off selected runways at ORD for specific runways...basically a Regulated Takeoff Graph (RTOG). Suggest ORD implement more RNAV SIDs...track distance on established procedures is key. Crews may want to consider requesting headings other than 180 on the ORD5 as well; or request other departure runways with more frequency.
Data retrieved from NASA's ASRS site 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.