Controller assumes aircraft is on RNAV approach; doesn't verify arrival assignment with pilot and ha...

Attributes
ACN	1156744
Time
Date	201403
Local Time Of Day	1801-2400
Place
Locale Reference	CLT.TRACON
State Reference	NC
Environment
Light	Dusk
Aircraft 1
Make Model Name	Light Transport Low Wing 2 Turbojet Eng
Operating Under FAR Part	Part 91
Flight Phase	Descent
Route In Use	STAR MAJIC1
Flight Plan	IFR
Aircraft 2
Make Model Name	A319
Operating Under FAR Part	Part 121
Flight Phase	Descent
Flight Plan	IFR
Person 1
Function	Approach
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 2
Person 2
Function	Captain
Qualification	Flight Crew Air Transport Pilot (ATP) Flight Crew Flight Instructor
Experience	Flight Crew Last 90 Days 60 Flight Crew Total 4500 Flight Crew Type 400
Events
Anomaly	ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Speed All Types
Miss Distance	Vertical 500

Narrative:

An atlanta center sector coordinated a jet direct sudsy intersection. I approved the request expecting the aircraft to be on the RNAV STAR. When the pilot checked in I verified his speed and he reported 250 KTS. I later asked the pilot whether or not he was descending via our opd and he responded no. I expected him to make the downwind turn at amobe; when he didn't I issued the aircraft a correcting vector then noticed that he had slowed to 200 KTS without advising me. I advised him to increase speed. I tried to turn and slow the opd arrival behind the business jet; but the reaction was not only too late but incorrect. Many factors went into my confusion in this scenario. The center controller never specified the arrival routing for the business jet; and I should have made him. The aircraft never reported slowing from his assigned speed. Had the pilot been at his assigned speed this event could have been prevented. Pilots reducing speed without notification is an all too common occurrence at clt. I should have made further inquiries to the pilot about his assigned arrival.

Original NASA ASRS Text

Title: Controller assumes aircraft is on RNAV approach; doesn't verify arrival assignment with pilot and has an operational error due to lack of speed control.

Narrative: An Atlanta Center sector coordinated a jet direct SUDSY Intersection. I approved the request expecting the aircraft to be on the RNAV STAR. When the pilot checked in I verified his speed and he reported 250 KTS. I later asked the pilot whether or not he was descending via our OPD and he responded no. I expected him to make the downwind turn at AMOBE; when he didn't I issued the aircraft a correcting vector then noticed that he had slowed to 200 KTS without advising me. I advised him to increase speed. I tried to turn and slow the OPD arrival behind the Business Jet; but the reaction was not only too late but incorrect. Many factors went into my confusion in this scenario. The Center Controller never specified the arrival routing for the Business Jet; and I should have made him. The aircraft never reported slowing from his assigned speed. Had the pilot been at his assigned speed this event could have been prevented. Pilots reducing speed without notification is an all too common occurrence at CLT. I should have made further inquiries to the pilot about his assigned arrival.

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