37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1368390 |
Time | |
Date | 201606 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | STL.Airport |
State Reference | MO |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | B737 Next Generation Undifferentiated |
Operating Under FAR Part | Part 121 |
Flight Phase | Parked |
Flight Plan | IFR |
Component | |
Aircraft Component | Aero Charts |
Person 1 | |
Function | First Officer |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 185 Flight Crew Type 11000 |
Events | |
Anomaly | Deviation - Procedural Published Material / Policy |
Narrative:
Stl natca 2 SID (runway 30L/right) requires a climb gradient of '500 feet per NM to woltr.' the performance chart all engine data does not show fixes such as woltr. This situation requires the pilot to notice the 'direct distance from lambert to st louis international (runway 30L/right) to: woltr 5 NM' in the fine print to the left of the SID ground track. And then the pilot must do a lot of mental math.minimum crossing altitude at woltr is 2500 feet. The field is approximately 600 feet MSL. Difference about 1900 feet. The track distance to woltr is slightly more than 5 NM since the chart says the 'direct distance' is 5 NM; but there is no way to actually calculate this difference. 1900 feet divided by 5 NM is about 380 feet per NM. Then the pilot can check the performance chart all engine data for 380 feet per NM up to 2500 feet.this process unnecessarily increases risk. There are many opportunities to make a mistake in the above thought process. Further; many pilots may fail to realize how to figure it out; or blow it off.please try to have all SID required climb gradients expressed in simple feet per NM to a final altitude; and eliminate those that require feet per NM to a waypoint.
Original NASA ASRS Text
Title: B737 First Officer discussed the complexity some aeronautical charts present when pilots are required to mentally calculate the required climb gradient in feet per mile on SIDs. For example; the STL NATCA2 RNAV did not have the calculation charted but did have a required departure waypoint minimum crossing altitude.
Narrative: STL NATCA 2 SID (Runway 30L/R) requires a climb gradient of '500 feet per NM to WOLTR.' The Performance Chart ALL ENG data does not show fixes such as WOLTR. This situation requires the Pilot to notice the 'Direct distance from Lambert to St Louis International (Runway 30L/R) to: WOLTR 5 NM' in the fine print to the left of the SID ground track. And then the Pilot must do a lot of mental math.Minimum crossing altitude at WOLTR is 2500 feet. The field is approximately 600 feet MSL. Difference about 1900 feet. The track distance to WOLTR is slightly more than 5 NM since the chart says the 'direct distance' is 5 NM; but there is no way to actually calculate this difference. 1900 feet divided by 5 NM is about 380 feet per NM. Then the Pilot can check the Performance Chart ALL ENG data for 380 feet per NM up to 2500 feet.This process unnecessarily increases RISK. There are many opportunities to make a mistake in the above thought process. Further; many Pilots may fail to realize how to figure it out; or blow it off.Please try to have all SID required climb gradients expressed in simple feet per NM to a final ALTITUDE; and eliminate those that require feet per NM to a waypoint.
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.