 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A be 350 pilot operating with a new avionics package had an altitude deviation after the autopilot did not capture the selected altitude during descent for approach. Confusion about FMS and autopilot functions and control locations contributed.
| Attributes | |
| ACN | 1000447 |
| Time | |
| Date | 201203 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | ZZZ.Airport |
| State Reference | US |
| Environment | |
| Flight Conditions | Mixed |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Super King Air 350 |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Initial Approach |
| Route In Use | Vectors |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | Flight Dynamics Navigation and Safety |
| Person 1 | |
| Qualification | Flight Crew Instrument Flight Crew Multiengine Flight Crew Flight Instructor Flight Crew Flight Engineer Flight Crew Air Transport Pilot (ATP) |
| Experience | Flight Crew Last 90 Days 10 Flight Crew Total 5000 Flight Crew Type 200 |
| Events | |
| Anomaly | Aircraft Equipment Problem Less Severe Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural Clearance Inflight Event / Encounter CFTT / CFIT |
Narrative:
During vector to final and descending below overcast layer; we did not level off with autopilot engaged. We disconnected autopilot and proceeded in VFR to join ILS. Controller gave us a low altitude alert as we were correcting and we thanked them for being alert. This was the first trip for pilot flying using this particular avionics package. It takes a little longer to correct things when you are not familiar with them as you question whether you are interpreting information correctly. FMS and autopilot systems work similarly; but have different ways and locations for annunciators. It's easy to think you have set something properly and then be forced to correct. This rapid correction can also prevent you from going back to see if something was 'set' or 'captured' or failed to 'engage' or 'capture.'
Original NASA ASRS Text
Title: A BE 350 Pilot operating with a new avionics package had an altitude deviation after the autopilot did not capture the selected altitude during descent for approach. Confusion about FMS and Autopilot functions and control locations contributed.
Narrative: During vector to final and descending below overcast layer; we did not level off with autopilot engaged. We disconnected autopilot and proceeded in VFR to join ILS. Controller gave us a low altitude alert as we were correcting and we thanked them for being alert. This was the first trip for pilot flying using this particular avionics package. It takes a little longer to correct things when you are not familiar with them as you question whether you are interpreting information correctly. FMS and autopilot systems work similarly; but have different ways and locations for annunciators. It's easy to think you have set something properly and then be forced to correct. This rapid correction can also prevent you from going back to see if something was 'set' or 'captured' or failed to 'engage' or 'capture.'
Data retrieved from NASA's ASRS site as of July 2013 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.