Air carrier requests opposite direction landing. ATC unable to comply. Pilot upset.

Attributes
ACN	200347
Time
Date	199201
Day	Sat
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : rdu
State Reference	NC
Altitude	msl bound lower : 9000 msl bound upper : 11000
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Controlling Facilities	tracon : rdu tower : fwa
Operator	common carrier : air carrier
Make Model Name	Medium Large Transport, Low Wing, 2 Turbojet Eng
Flight Phase	descent other landing other
Route In Use	approach : visual
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : approach
Qualification	controller : radar
ASRS Report	200347
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	other anomaly other other anomaly other
Independent Detector	other controllera
Resolutory Action	none taken : unable
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	other

Narrative:

Air carrier X came in at 11000 ft, I descended aircraft to 9000 ft and advised him he would get runway 23L. He acknowledged this transmission. We were advertising runway 23L/right all night long. When air carrier X was 13 mi southwest of airport he asked if winds were calm and if he could land opposite direction. I advised him he couldn't due to departure traffic. When he was downwind abeam the airport he once again blocked the frequency by asking where his conflicting traffic was. He was clearly upset because he didn't like the procedure he could call the facility and discuss it with management. He replied 'if they are anything like you I don't want to.' this is very typical of how pilots that fly into rdu treat the ATC specialists on frequency. This has caused several dangerous situations because while these unprofessional pilots are using up the frequency other aircraft are fast approaching a precarious position since ATC can't issue much needed instructions. FAA management at rdu refuses to take action to fix this dangerous situation.

Original NASA ASRS Text

Title: ACR REQUESTS OPPOSITE DIRECTION LNDG. ATC UNABLE TO COMPLY. PLT UPSET.

Narrative: ACR X CAME IN AT 11000 FT, I DSNDED ACFT TO 9000 FT AND ADVISED HIM HE WOULD GET RWY 23L. HE ACKNOWLEDGED THIS XMISSION. WE WERE ADVERTISING RWY 23L/R ALL NIGHT LONG. WHEN ACR X WAS 13 MI SW OF ARPT HE ASKED IF WINDS WERE CALM AND IF HE COULD LAND OPPOSITE DIRECTION. I ADVISED HIM HE COULDN'T DUE TO DEP TFC. WHEN HE WAS DOWNWIND ABEAM THE ARPT HE ONCE AGAIN BLOCKED THE FREQ BY ASKING WHERE HIS CONFLICTING TFC WAS. HE WAS CLRLY UPSET BECAUSE HE DIDN'T LIKE THE PROC HE COULD CALL THE FACILITY AND DISCUSS IT WITH MGMNT. HE REPLIED 'IF THEY ARE ANYTHING LIKE YOU I DON'T WANT TO.' THIS IS VERY TYPICAL OF HOW PLTS THAT FLY INTO RDU TREAT THE ATC SPECIALISTS ON FREQ. THIS HAS CAUSED SEVERAL DANGEROUS SITUATIONS BECAUSE WHILE THESE UNPROFESSIONAL PLTS ARE USING UP THE FREQ OTHER ACFT ARE FAST APCHING A PRECARIOUS POS SINCE ATC CAN'T ISSUE MUCH NEEDED INSTRUCTIONS. FAA MGMNT AT RDU REFUSES TO TAKE ACTION TO FIX THIS DANGEROUS SITUATION.

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.