37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1695201 |
Time | |
Date | 201910 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Gulfstream IV / G350 / G450 |
Operating Under FAR Part | Part 91 |
Flight Phase | Final Approach |
Route In Use | Visual Approach |
Flight Plan | IFR |
Component | |
Aircraft Component | Autopilot |
Person 1 | |
Function | Pilot Not Flying Captain |
Qualification | Flight Crew Multiengine Flight Crew Air Transport Pilot (ATP) Flight Crew Instrument |
Events | |
Anomaly | Deviation - Procedural Published Material / Policy Deviation - Speed All Types Inflight Event / Encounter Unstabilized Approach |
Narrative:
During a visual approach to ZZZ; I was the pilot monitoring during a visual approach to runway xxl. The pilot flying was a highly experienced PIC hand-flying a right base to final. There were multiple aircraft in the pattern at ZZZ including training aircraft to the parallel runway to the west and helicopter traffic to the east of our runway. During the base to final turn; I was preoccupied with maintaining visual separation from a cessna that appeared to be overshooting his runway to our right and a helicopter to our left that was approaching to land on the east ramp. After rolling out on final; I noticed that the pilot flying had selected an altitude below field elevation in the altitude alerter without calling it and also selected flight level change on the guidance panel. This had caused the autothrottles to pull back to flight idle and the speed had decayed to approximately reference minus 10-15 kts and the stall awareness bars had appeared in the pfd. I called 'speed way low' and the pilot flying had already seen it; disconnected autothrottle; added power; and reduced pitch to recover correct speed. Correct approach speed was quickly obtained; the approach was stabilized prior to 500 feet; and we continued to a normal landing.despite having trained multiple times in recent years to avoid this exact scenario; the 'flch trap' continues to be an issue. Personally; I never use flch for descents for exactly that reason but I am reluctant to correct a 'technique' utilized by a fellow pilot; including the use of flch for descent. The company has rightly prohibited the use of flch during 'approaches' but its use during visual approach is something of a gray area. I believe the use of flight level change should be prohibited for all descents below 5;000 feet AGL. In my opinion; flch is the most dangerous button on the flight guidance panel. As the pilot monitoring; it was my job to make sure the proper flight path and energy state of the aircraft were maintained but the distraction of multiple aircraft in close proximity and a 'traffic; traffic' TCAS alert forced greater attention outside the cockpit than inside. In the future; I will be more proactive in refusing to allow my flying partner to utilize flight level change.
Original NASA ASRS Text
Title: G450 pilot reported selecting an incorrect autopilot mode during approach that resulted in excessively slow airspeed.
Narrative: During a visual approach to ZZZ; I was the pilot monitoring during a visual approach to Runway XXL. The Pilot Flying was a highly experienced PIC hand-flying a right base to final. There were multiple aircraft in the pattern at ZZZ including training aircraft to the parallel runway to the west and helicopter traffic to the east of our runway. During the base to final turn; I was preoccupied with maintaining visual separation from a Cessna that appeared to be overshooting his runway to our right and a helicopter to our left that was approaching to land on the east ramp. After rolling out on final; I noticed that the pilot flying had selected an altitude below field elevation in the altitude alerter without calling it and also selected Flight Level Change on the guidance panel. This had caused the autothrottles to pull back to flight idle and the speed had decayed to approximately REF minus 10-15 kts and the stall awareness bars had appeared in the PFD. I called 'speed way low' and the pilot flying had already seen it; disconnected autothrottle; added power; and reduced pitch to recover correct speed. Correct approach speed was quickly obtained; the approach was stabilized prior to 500 feet; and we continued to a normal landing.Despite having trained multiple times in recent years to avoid this exact scenario; the 'FLCH Trap' continues to be an issue. Personally; I NEVER use FLCH for descents for exactly that reason but I am reluctant to correct a 'technique' utilized by a fellow pilot; including the use of FLCH for descent. The company has rightly prohibited the use of FLCH during 'approaches' but its use during visual approach is something of a gray area. I believe the use of Flight Level Change should be PROHIBITED FOR ALL DESCENTS below 5;000 feet AGL. In my opinion; FLCH is the most dangerous button on the Flight Guidance Panel. As the pilot monitoring; it was my job to make sure the proper flight path and energy state of the aircraft were maintained but the distraction of multiple aircraft in close proximity and a 'Traffic; Traffic' TCAS alert forced greater attention OUTSIDE the cockpit than inside. In the future; I will be more proactive in refusing to allow my flying partner to utilize Flight Level Change.
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.