Pilot of a beech BE55, baron, failed to have his altitude transponder system checked after ATC notified him of an indicating error. At least reporter advised ATC that he was indicating at the assigned altitude even though ATC showed him at a higher altitude. The reporter continued flight after his next subsequent landing in class C airspace.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	374840
Time
Date	199707
Day	Mon
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : ord
State Reference	IL
Altitude	msl bound lower : 9000 msl bound upper : 9000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : ord tower : slc
Operator	general aviation : corporate
Make Model Name	Baron 55/Cochise
Operating Under FAR Part	Part 91
Flight Phase	cruise other
Flight Plan	IFR
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	other other : other pilot : instrument pilot : cfi pilot : commercial
Experience	flight time last 90 days : 110 flight time total : 1300 flight time type : 220
ASRS Report	374840
Person 2
Affiliation	government : faa
Function	controller : approach
Qualification	controller : radar
Events
Anomaly	aircraft equipment problem : less severe non adherence : far other anomaly other
Independent Detector	other controllera
Resolutory Action	other other
Consequence	Other
Supplementary
Primary Problem	Aircraft
Air Traffic Incident	Pilot Deviation

Narrative:

At 9000 ft MSL in ZAU's airspace, I was informed that my transponder in small aircraft was indicating high, so I reset transponder and it still indicated high, so I was told to stop 'altitude' squawk. At the next handoff to another facility, they didn't state that it was off. They asked me to cycle it on again. I landed in lan class C without mention of the error, and I departed later in the day because I didn't see a problem, nor was I notified of an error by lan approach. I hope the problem doesn't reoccur as I just had a transponder check 3 months prior.

Original NASA ASRS Text

Title: PLT OF A BEECH BE55, BARON, FAILED TO HAVE HIS ALT XPONDER SYS CHKED AFTER ATC NOTIFIED HIM OF AN INDICATING ERROR. AT LEAST RPTR ADVISED ATC THAT HE WAS INDICATING AT THE ASSIGNED ALT EVEN THOUGH ATC SHOWED HIM AT A HIGHER ALT. THE RPTR CONTINUED FLT AFTER HIS NEXT SUBSEQUENT LNDG IN CLASS C AIRSPACE.

Narrative: AT 9000 FT MSL IN ZAU'S AIRSPACE, I WAS INFORMED THAT MY XPONDER IN SMA WAS INDICATING HIGH, SO I RESET XPONDER AND IT STILL INDICATED HIGH, SO I WAS TOLD TO STOP 'ALT' SQUAWK. AT THE NEXT HDOF TO ANOTHER FACILITY, THEY DIDN'T STATE THAT IT WAS OFF. THEY ASKED ME TO CYCLE IT ON AGAIN. I LANDED IN LAN CLASS C WITHOUT MENTION OF THE ERROR, AND I DEPARTED LATER IN THE DAY BECAUSE I DIDN'T SEE A PROB, NOR WAS I NOTIFIED OF AN ERROR BY LAN APCH. I HOPE THE PROB DOESN'T REOCCUR AS I JUST HAD A XPONDER CHK 3 MONTHS PRIOR.

Data retrieved from NASA's ASRS site as of July 2007 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.