ARTCC radar controller mistakenly cleared an air carrier FK10 to the same altitude as a BE20 but put the wrong altitude in the air carrier's data block. The controller gave the air carrier traffic information on the BE20 and the air carrier received a TCASII RA and stopped his climb, but not before less than standard separation occurred.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	367353
Time
Date	199704
Day	Wed
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : vwv
State Reference	OH
Altitude	msl bound lower : 22000 msl bound upper : 23000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zob
Operator	common carrier : air carrier
Make Model Name	Fokker 100
Operating Under FAR Part	Part 121
Navigation In Use	Other
Flight Phase	climbout : intermediate altitude
Route In Use	enroute : on vectors
Flight Plan	IFR
Aircraft 2
Operator	general aviation : personal
Make Model Name	Super King Air 200/Huron
Operating Under FAR Part	Part 91
Flight Phase	cruise other
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : radar
Qualification	controller : radar
Experience	controller radar : 8
ASRS Report	367353
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 160 flight time total : 10000
ASRS Report	367602
Events
Anomaly	conflict : airborne less severe non adherence : required legal separation non adherence : published procedure
Independent Detector	aircraft equipment other aircraft equipment : unspecified other controllera other flight crewa
Resolutory Action	flight crew : took evasive action
Consequence	Other
Miss Distance	horizontal : 24000 vertical : 300
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Error

Narrative:

The king air was at FL230 sebound when the air carrier FK10 came on my frequency. I meant to climb him to FL22O and I even put it in the data block, but I issued FL230 and he read back FL230. Supplemental information from acn 367602: climbing out of dtw to clt. Flight was cleared to FL230. Center advised king air traffic at our 1 O'clock position. We acquired aircraft on TCASII at +1300 and we got a TCASII RA. We leveled at FL220 as the king air passed above TCASII registered +900 ft of separation when it was approximately 1-2 mi behind us, TCASII gave clear of conflict advisory and we continued up to FL230. Center said verify at FL220 to us and we advised 'no, we were at FL230.' if we were given an amended clearance we never heard nor acknowledged it. No abrupt maneuvers were made.

Original NASA ASRS Text

Title: ARTCC RADAR CTLR MISTAKENLY CLRED AN ACR FK10 TO THE SAME ALT AS A BE20 BUT PUT THE WRONG ALT IN THE ACR'S DATA BLOCK. THE CTLR GAVE THE ACR TFC INFO ON THE BE20 AND THE ACR RECEIVED A TCASII RA AND STOPPED HIS CLB, BUT NOT BEFORE LTSS OCCURRED.

Narrative: THE KING AIR WAS AT FL230 SEBOUND WHEN THE ACR FK10 CAME ON MY FREQ. I MEANT TO CLB HIM TO FL22O AND I EVEN PUT IT IN THE DATA BLOCK, BUT I ISSUED FL230 AND HE READ BACK FL230. SUPPLEMENTAL INFO FROM ACN 367602: CLBING OUT OF DTW TO CLT. FLT WAS CLRED TO FL230. CTR ADVISED KING AIR TFC AT OUR 1 O'CLOCK POS. WE ACQUIRED ACFT ON TCASII AT +1300 AND WE GOT A TCASII RA. WE LEVELED AT FL220 AS THE KING AIR PASSED ABOVE TCASII REGISTERED +900 FT OF SEPARATION WHEN IT WAS APPROX 1-2 MI BEHIND US, TCASII GAVE CLR OF CONFLICT ADVISORY AND WE CONTINUED UP TO FL230. CTR SAID VERIFY AT FL220 TO US AND WE ADVISED 'NO, WE WERE AT FL230.' IF WE WERE GIVEN AN AMENDED CLRNC WE NEVER HEARD NOR ACKNOWLEDGED IT. NO ABRUPT MANEUVERS WERE MADE.

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.