A BE10 flight crew reports having taken evasive action while at cruise to avoid an aircraft that descended from a flight level down to below the assigned altitude. The reporter surmised that the other aircraft's pilot had not reset the altimeter during the descent below FL180.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	334555
Time
Date	199604
Day	Thu
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : jot
State Reference	IL
Altitude	msl bound lower : 10000 msl bound upper : 10300
Environment
Flight Conditions	Mixed
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zau tower : azo
Operator	common carrier : air taxi
Make Model Name	King Air 100 A/B
Operating Under FAR Part	Part 135
Flight Phase	cruise other
Route In Use	enroute airway : zau
Flight Plan	IFR
Aircraft 2
Make Model Name	Super King Air 200/Huron
Operating Under FAR Part	other : unknown
Flight Phase	descent other
Flight Plan	IFR
Person 1
Affiliation	company : air taxi
Function	flight crew : first officer
Qualification	pilot : commercial pilot : instrument
ASRS Report	334555
Person 2
Affiliation	company : air taxi
Function	flight crew : captain oversight : pic
Qualification	pilot : commercial pilot : instrument
ASRS Report	334554
Events
Anomaly	altitude deviation : overshoot non adherence : clearance other anomaly other
Independent Detector	other flight crewa
Resolutory Action	flight crew : took evasive action other other
Consequence	Other
Miss Distance	horizontal : 600 vertical : 300
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

We were level 10000 ft and northbound on V69. We had the current altimeter setting (29.29) in our altimeters. I heard the king air 200 receive his descent clearance to 11000 ft. I was the PF in the right seat. While level, I noticed the red and white BE20 ahead and to the right (I could read his n-number). We inquired with ATC about the previously referred to traffic's altitude. (I knew about the traffic but was not given an advisory pertaining to it, the controller only said there was traffic above us which was preventing our climb to 15000 ft.) the controller instructed the king air to maintain 11000 ft. I had taken evasive action by turning away from the other aircraft. After the other king air was reissued his clearance we noticed him begin his climb back up to 11000 ft. The other king air had descended from FL190 and it is my belief that he did not reset his altimeter. This would have resulted in his altimeter indicating in excess of 600 ft off.

Original NASA ASRS Text

Title: A BE10 FLC RPTS HAVING TAKEN EVASIVE ACTION WHILE AT CRUISE TO AVOID AN ACFT THAT DSNDED FROM A FLT LEVEL DOWN TO BELOW THE ASSIGNED ALT. THE RPTR SURMISED THAT THE OTHER ACFT'S PLT HAD NOT RESET THE ALTIMETER DURING THE DSCNT BELOW FL180.

Narrative: WE WERE LEVEL 10000 FT AND NBOUND ON V69. WE HAD THE CURRENT ALTIMETER SETTING (29.29) IN OUR ALTIMETERS. I HEARD THE KING AIR 200 RECEIVE HIS DSCNT CLRNC TO 11000 FT. I WAS THE PF IN THE R SEAT. WHILE LEVEL, I NOTICED THE RED AND WHITE BE20 AHEAD AND TO THE R (I COULD READ HIS N-NUMBER). WE INQUIRED WITH ATC ABOUT THE PREVIOUSLY REFERRED TO TFC'S ALT. (I KNEW ABOUT THE TFC BUT WAS NOT GIVEN AN ADVISORY PERTAINING TO IT, THE CTLR ONLY SAID THERE WAS TFC ABOVE US WHICH WAS PREVENTING OUR CLB TO 15000 FT.) THE CTLR INSTRUCTED THE KING AIR TO MAINTAIN 11000 FT. I HAD TAKEN EVASIVE ACTION BY TURNING AWAY FROM THE OTHER ACFT. AFTER THE OTHER KING AIR WAS REISSUED HIS CLRNC WE NOTICED HIM BEGIN HIS CLB BACK UP TO 11000 FT. THE OTHER KING AIR HAD DSNDED FROM FL190 AND IT IS MY BELIEF THAT HE DID NOT RESET HIS ALTIMETER. THIS WOULD HAVE RESULTED IN HIS ALTIMETER INDICATING IN EXCESS OF 600 FT OFF.

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.