37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1159270 |
Time | |
Date | 201403 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | PHX.Airport |
State Reference | AZ |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Gulfstream V / G500 / G550 |
Operating Under FAR Part | Part 135 |
Flight Phase | Descent |
Route In Use | STAR EAGUL5 |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Flying Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 120 Flight Crew Total 14500 Flight Crew Type 600 |
Events | |
Anomaly | Deviation - Altitude Crossing Restriction Not Met Deviation - Procedural FAR Deviation - Procedural Clearance Deviation - Speed All Types |
Narrative:
Descending on the EAGUL5 into phx; center cleared us direct homrr with no speed restriction until reaching homrr. The STAR requires crossing homrr at or below 16;000 ft at 250 KTS. The FMS was programmed with the arrival; and VNAV was selected as well. All seemed well as we descended to and crossed homrr at 16;000 ft/250 KTS. However the next fix vnnom required crossing between 11;000 ft and 10;000 ft vnnom is 4.1 NM from homrr. Crossing homrr at 16;000 ft; we realized that it was almost impossible to lose 5;000 ft to 6;000 ft in 4.1 NM. At this point I clicked off the automation and pointed the nose down; achieving a descent rate of better than 6;000 FPM. Our airspeed increased to 280 KTS and we crossed vnnom high and fast. I do not believe that we caused a conflict with any other aircraft.I have flown many; many VNAV stars in this aircraft; and it has never been off before. The STAR called for crossing homrr at or below 16;000 ft; and the FMS should have been in a position to make the next subsequent fix.obviously we could have done a better job monitoring the situation; however this occurred during an extremely high workload period. We made; programmed and verified 2 runway/ approach changes during this descent prior to homrr. In fact the first change went from a landing east flow to a landing west flow. This could actually explain why the FMS logic chose 16;000 ft at homrr instead of lower....landing east on the EAGUL5 requires crossing a different fix immediately past homrr (smaak) between 15;000 ft and 14;000 ft.this is a really poorly designed STAR. Something should be done to warn other crews not to fall into the same trap that we did.
Original NASA ASRS Text
Title: When; while descending via the EAGUL RNAV STAR to PHX; their FMS system failed to compute the need to cross HOMRR well below the maximum 16;000 FT in order to cross VNNOM 4.1 NM later between 11;000 FT and 10;000 FT; the flight crew initiated an expedited descent and exceeded the 250 KTS charted max IAS. Multiple runway changes by ATC; including a switch from a downwind arrival to land east to straight in to land west were cited by the reporter as likely contributing factors.
Narrative: Descending on the EAGUL5 into PHX; Center cleared us direct HOMRR with no speed restriction until reaching HOMRR. The STAR requires crossing HOMRR at or below 16;000 FT at 250 KTS. The FMS was programmed with the arrival; and VNAV was selected as well. All seemed well as we descended to and crossed HOMRR at 16;000 FT/250 KTS. However the next fix VNNOM required crossing between 11;000 FT and 10;000 FT VNNOM is 4.1 NM from HOMRR. Crossing HOMRR at 16;000 FT; we realized that it was almost impossible to lose 5;000 FT to 6;000 FT in 4.1 NM. At this point I clicked off the automation and pointed the nose down; achieving a descent rate of better than 6;000 FPM. Our airspeed increased to 280 KTS and we crossed VNNOM high and fast. I do not believe that we caused a conflict with any other aircraft.I have flown many; many VNAV STARs in this aircraft; and it has never been off before. The STAR called for crossing HOMRR at or below 16;000 FT; and the FMS should have been in a position to make the next subsequent fix.Obviously we could have done a better job monitoring the situation; however this occurred during an extremely high workload period. We made; programmed and verified 2 runway/ approach changes during this descent prior to HOMRR. In fact the first change went from a landing east flow to a landing west flow. This could actually explain why the FMS logic chose 16;000 FT at HOMRR instead of lower....Landing east on the EAGUL5 requires crossing a different fix immediately past HOMRR (SMAAK) between 15;000 FT and 14;000 FT.This is a really poorly designed STAR. Something should be done to warn other crews not to fall into the same trap that we did.
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.