37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1033140 |
Time | |
Date | 201208 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Baron 55/Cochise |
Operating Under FAR Part | Part 91 |
Flight Phase | Climb |
Route In Use | Vectors |
Flight Plan | IFR |
Component | |
Aircraft Component | Autopilot |
Person 1 | |
Function | Single Pilot Pilot Flying |
Qualification | Flight Crew Flight Instructor Flight Crew Flight Engineer Flight Crew Air Transport Pilot (ATP) Flight Crew Instrument Flight Crew Multiengine |
Experience | Flight Crew Last 90 Days 143 Flight Crew Total 10843 Flight Crew Type 50 |
Events | |
Anomaly | Deviation - Altitude Overshoot Deviation - Procedural Clearance Inflight Event / Encounter Weather / Turbulence |
Narrative:
I was on an IFR clearance and was given runway heading to 3;000 ft. Upon checking in with approach I was given a heading of 020 degrees and a further climb to 5;000 ft. After reading back my clearance I advised approach what heading I needed to avoid thunderstorms. Shortly after; while approaching 5;000 ft; I was cleared to my final filed altitude of 6;000 ft and cleared on course. I entered 6;000 ft in my reminder and looked at the ipad that I was carrying in the aircraft. This aircraft is owned by another person and they had onboard wifi and no radar. The autopilot was on; but there was no altitude pre-select requiring me to select altitude hold. The airplane was climbing and starting the turn as I looked down at the ipad to determine if the on course heading that I had chosen would keep me clear of the thunderstorm cells in the area. As my scan crossed the altimeter I noticed that I had blown through 6;000 ft and had almost reached 6;500 ft. I immediately disconnected the autopilot and continued the turn to my on course heading while smoothly lowering my nose and descending to 6;000 ft. After quickly reaching 6;000 ft I received no call from approach. This was [the] first day that I had flown this airplane; and the third of four legs on this day. I have a baron of my own; but they are very different; different panel; different autopilot; different scan. My aircraft has an altitude alerter. My unfamiliarity with the airplane and its controls was a contributing factor. Another contributing factor was multiple altitude and heading changes in a short period while trying to maintain good situation awareness with regard to weather avoidance. A further contributing factor was operating as a single pilot. I'm a major airline pilot by profession and I'm used to having a second pilot to double check me. Having to aviate; navigate and communicate in an unfamiliar aircraft while avoiding weather helped lead to a brief altitude deviation. Fortunately; I was not in congested airspace and there was no conflict.
Original NASA ASRS Text
Title: B55 pilot attributed an altitude overshoot to lack of familiartity with the aircraft's autopilot; a succession of altitude and heading instructions from ATC; and weather avoidance.
Narrative: I was on an IFR clearance and was given runway heading to 3;000 FT. Upon checking in with Approach I was given a heading of 020 degrees and a further climb to 5;000 FT. After reading back my clearance I advised Approach what heading I needed to avoid thunderstorms. Shortly after; while approaching 5;000 FT; I was cleared to my final filed altitude of 6;000 FT and cleared on course. I entered 6;000 FT in my reminder and looked at the iPad that I was carrying in the aircraft. This aircraft is owned by another person and they had onboard WiFi and no radar. The autopilot was on; but there was no altitude pre-select requiring me to select altitude hold. The airplane was climbing and starting the turn as I looked down at the iPad to determine if the on course heading that I had chosen would keep me clear of the thunderstorm cells in the area. As my scan crossed the altimeter I noticed that I had blown through 6;000 FT and had almost reached 6;500 FT. I immediately disconnected the autopilot and continued the turn to my on course heading while smoothly lowering my nose and descending to 6;000 FT. After quickly reaching 6;000 FT I received no call from Approach. This was [the] first day that I had flown this airplane; and the third of four legs on this day. I have a Baron of my own; but they are very different; different panel; different autopilot; different scan. My aircraft has an altitude alerter. My unfamiliarity with the airplane and its controls was a contributing factor. Another contributing factor was multiple altitude and heading changes in a short period while trying to maintain good situation awareness with regard to weather avoidance. A further contributing factor was operating as a single pilot. I'm a major airline pilot by profession and I'm used to having a second pilot to double check me. Having to aviate; navigate and communicate in an unfamiliar aircraft while avoiding weather helped lead to a brief altitude deviation. Fortunately; I was not in congested airspace and there was no conflict.
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.