Date: 201310
Local time of day: 1201-1800
Location: CID.TRACON, IA
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Bonanza 35
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Initial Climb
Airspace: Class C CID
ATC / advisory: TRACON CID
Aircraft component: Pitot-Static System
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Flight Instructor; Flight Crew Commercial
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Maintenance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Overcame Equipment Problem; General Maintenance Action
Contributing factors: Aircraft; Human Factors; Procedure
Primary problem: Human Factors

Narrative: Prior to conducting the VFR flight a thorough preflight check was conducted and no discrepancies were noted. The altimeter setting was compared to the field elevation and the altimeter was noted to be approximately 20 FT low but was determined to be within acceptable limits. During takeoff and climb; the airspeed indicator; vertical speed indicator (VSI) and altimeter all appeared to be indicating correctly; although the VSI and altimeter seemed a bit sluggish during the climb. After contacting departure; I noticed that the altimeter froze at 1;500 FT; even though the airplane was still clearly climbing. ATC asked to confirm altitude; which I reported as 1;500 FT. I noted that the backup GPS altimeter was indicating 2;500 FT; and I reported the discrepancy to ATC accordingly. ATC requested me to recycle altitude squawk reporting but the issue persisted. ATC finally requested that I stop squawking mode C altitude reporting. At this point I was about 20 miles from [the destination airport]; so I elected to land as planned; and used the GPS altitude as backup. I completed the flight without incident. After landing I had a Mechanic take a look at the pitot-static system. The Mechanic removed the airspeed indicator and found that the pitot line and the static line were swapped on the airspeed indicator. The Mechanic corrected the issue and reinstalled the airspeed indicator. Although my flight to ultimately completed safely; there are several factors about this situation that I find extremely alarming and worthy of some lessons learned. 1.) This airplane has just completed a pitot-static altimeter inspection several weeks prior with no unusual findings reported by the Mechanic. 2.) Performing the preflight checks specified by the AFM/POH did not reveal anything unusual about the altimeter or pitot-static system. 3.) Had this flight been conducted IFR in IMC and had I not had a backup altitude source; this flight could have had a very different outcome. This situation has taught me several lessons that I think every pilot should consider. First is trust; but verify; the work done by your mechanics at each inspection. Second; conduct a thorough ground and flight checkout of your aircraft after any inspection; especially before you plan on flying in hard IMC. And finally; have a backup plan; and backup equipment.




Synopsis: The pilot of a Beechcraft Bonanza experienced a frozen altimeter and associated transponder readout while conducting a VFR flight. During maintenance troubleshooting it was discovered that the pitot and static lines had been reversed on the altimeter; presumably during the recent pitot/static inspection.