37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 872810 |
Time | |
Date | 201002 |
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 | Skylane 182/RG Turbo Skylane/RG |
Operating Under FAR Part | Part 91 |
Flight Phase | Initial Climb |
Route In Use | Vectors |
Flight Plan | None |
Aircraft 2 | |
Make Model Name | Fighting Falcon F16 |
Flight Phase | Cruise |
Component | |
Aircraft Component | Autopilot |
Person 1 | |
Function | Pilot Flying |
Qualification | Flight Crew Flight Instructor Flight Crew Instrument Flight Crew Commercial |
Experience | Flight Crew Last 90 Days 30 Flight Crew Total 750 Flight Crew Type 45 |
Events | |
Anomaly | Conflict NMAC Deviation - Altitude Overshoot Deviation - Procedural Published Material / Policy |
Miss Distance | Horizontal 0 Vertical 400 |
Narrative:
C182T with KAP140 autopilot requires altimeter setting to be entered three times. Altimeter was 30.33; but G1000 & KAP140 autopilot were incorrectly set to 30.03; standby altimeter was set correctly. Pre-takeoff crosscheck missed the altimeter setting mismatch. Flight was a practice IFR flight in VFR with a safety pilot. On initial climbout as we switched to approach; were given vector heading 210 and climb to 3000. Set the KAP140 to 3000; and G1000 altitude to 3000. As we passed through 2650 on G1000; noticed standby altitude showed 3000; called ATC for altitude check; told 3150; mismatch on G1000 altimeter and standby; disconnected KAP140 and descended to 3000 on standby altimeter. A pair of F-16's flew overhead 400 feet during this time period. We were VFR and a visual on the F-16's during this period of time. Identified that altimeter was incorrectly set to 30.03 instead of 30.33. Controller allowed us to proceed on course and climb to 3500 afterwards; he asked if we understood we were to maintain 3000; we said we understood. He said that there was traffic above us. The controller was very professional. G1000 with KAP1000 require multiple altimeter settings; similar numbers must be carefully verified each time. Cross check more than once and always verify field elevation in both the G1000 and round dial altimeter. The similarity of the numbers appeared the same; the PIC was used to flying round-dials recently and verified the field elevation in the standby altimeter; but didn't compare the G1000 altitude and standby prior to takeoff; unknown why not. Initial climbout was busy time with climb checklists; contact approach; setting up autopilot; so problem with altimeter was not caught until passing 3000 on the standby altimeter. G1000 takes regular simulator practice to setup and make use of all the features. The lack of a KAP140 simulator with the G1000 simulator makes for the need of constant vigilance on cross-check.
Original NASA ASRS Text
Title: C182 pilot entered incorrect barometric altimeter setting for the G1000 and KAP140 autopilot prior to departure. The standyby altimeter was correctly set at 30.33 while 30.03 had been used elsewhere; resulting in an NMAC with F16's during initial climb.
Narrative: C182T with KAP140 autopilot requires altimeter setting to be entered three times. Altimeter was 30.33; but G1000 & KAP140 autopilot were incorrectly set to 30.03; Standby Altimeter was set correctly. Pre-takeoff crosscheck missed the Altimeter setting mismatch. Flight was a practice IFR flight in VFR with a safety pilot. On initial climbout as we switched to Approach; were given vector heading 210 and climb to 3000. Set the KAP140 to 3000; and G1000 ALT to 3000. As we passed through 2650 on G1000; noticed standby ALT showed 3000; called ATC for altitude check; told 3150; mismatch on G1000 altimeter and standby; disconnected KAP140 and descended to 3000 on Standby Altimeter. A pair of F-16's flew overhead 400 feet during this time period. We were VFR and a visual on the F-16's during this period of time. Identified that Altimeter was incorrectly set to 30.03 instead of 30.33. Controller allowed us to proceed on course and climb to 3500 afterwards; he asked if we understood we were to maintain 3000; we said we understood. He said that there was traffic above us. The controller was very professional. G1000 with KAP1000 require multiple altimeter settings; similar numbers must be carefully verified each time. Cross check more than once and always verify field elevation in both the G1000 and round dial altimeter. The similarity of the numbers appeared the same; the PIC was used to flying round-dials recently and verified the field elevation in the Standby Altimeter; but didn't compare the G1000 altitude and standby prior to takeoff; unknown why not. Initial climbout was busy time with climb checklists; contact approach; setting up autopilot; so problem with altimeter was not caught until passing 3000 on the Standby Altimeter. G1000 takes regular simulator practice to setup and make use of all the features. The lack of a KAP140 simulator with the G1000 simulator makes for the need of constant vigilance on cross-check.
Data retrieved from NASA's ASRS site as of April 2012 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.