Approach and local controller at cvg report frequent problems with air carrier aircraft using simila...

Attributes
ACN	595528
Time
Date	200310
Day	Fri
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : cvg.airport
State Reference	OH
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	Regional Jet 200 ER&LR
Operating Under FAR Part	Part 121
Flight Phase	climbout : takeoff ground : taxi
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : local
Experience	controller radar : 9
ASRS Report	595528
Person 2
Affiliation	government : faa
Function	controller : ground
Events
Anomaly	non adherence : published procedure non adherence : clearance other anomaly other
Independent Detector	other controllera other controllerb other flight crewa
Resolutory Action	none taken : anomaly accepted
Supplementary
Problem Areas	ATC Human Performance Flight Crew Human Performance
Primary Problem	Ambiguous

Narrative:

Aircraft X called and received taxi clearance to runway 36L during XA00 push. Aircraft received at least 2 xmissions from ground control. I was working local position. I put aircraft X into position after an arrival landed. My next xmissions was a takeoff clearance. About midway down the runway, another company aircraft advised he was ready to taxi. Gcw recalled the call sign and verified his call sign and destination. I then asked the aircraft after airborne to verify he was aircraft X and to verify his destination. He advised he was aircraft Y and correctly stated his destination. Fortunately, his initial flight plan was the same as aircraft X. I figure he received at least 4 ATC instructions and responded with the incorrect flight number. Pilots must be responsible for readback/hearback issues, as well as controllers, and should question things that 'just don't seem right.'

Original NASA ASRS Text

Title: APCH AND LCL CTLR AT CVG RPT FREQUENT PROBS WITH ACR ACFT USING SIMILAR FLT NUMBERS.

Narrative: ACFT X CALLED AND RECEIVED TAXI CLRNC TO RWY 36L DURING XA00 PUSH. ACFT RECEIVED AT LEAST 2 XMISSIONS FROM GND CTL. I WAS WORKING LCL POS. I PUT ACFT X INTO POS AFTER AN ARR LANDED. MY NEXT XMISSIONS WAS A TKOF CLRNC. ABOUT MIDWAY DOWN THE RWY, ANOTHER COMPANY ACFT ADVISED HE WAS READY TO TAXI. GCW RECALLED THE CALL SIGN AND VERIFIED HIS CALL SIGN AND DEST. I THEN ASKED THE ACFT AFTER AIRBORNE TO VERIFY HE WAS ACFT X AND TO VERIFY HIS DEST. HE ADVISED HE WAS ACFT Y AND CORRECTLY STATED HIS DEST. FORTUNATELY, HIS INITIAL FLT PLAN WAS THE SAME AS ACFT X. I FIGURE HE RECEIVED AT LEAST 4 ATC INSTRUCTIONS AND RESPONDED WITH THE INCORRECT FLT NUMBER. PLTS MUST BE RESPONSIBLE FOR READBACK/HEARBACK ISSUES, AS WELL AS CTLRS, AND SHOULD QUESTION THINGS THAT 'JUST DON'T SEEM RIGHT.'

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.

Approach and local controller at cvg report frequent problems with air carrier aircraft using similar flight numbers.