Air carrier captain challenges phl approach controller numerous times to verify clearance.

Attributes
ACN	544768
Time
Date	200204
Day	Tue
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : phl.airport
State Reference	PA
Altitude	msl single value : 3000
Environment
Flight Conditions	VMC
Light	Night Daylight
Aircraft 1
Controlling Facilities	tracon : phl.tracon
Operator	common carrier : air carrier
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 121
Flight Phase	descent : approach
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : multi engine pilot : instrument pilot : commercial pilot : cfi pilot : atp pilot : flight engineer
Experience	flight time last 90 days : 100 flight time total : 6000 flight time type : 1500
ASRS Report	544768
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Events
Anomaly	non adherence : published procedure
Independent Detector	other flight crewa
Resolutory Action	other
Supplementary
Problem Areas	ATC Human Performance
Primary Problem	ATC Human Performance
Situations
ATC Facility	procedure or policy : phl.tracon

Narrative:

Phl airport-we received an approach clearance that was partially blocked by another aircraft radio call. We readback the clearance with 'confirm'. Controller did not respond, so we asked him to repeat the clearance again, no response. We asked 'please confirm' with our call sign and the clearance we believed to have received. The controller responded with 'yes,' very loudly and nothing else. A few seconds later, he told us to contact tower and we completed the flight uneventfully. The airport was very busy, but without controller responsibility to correct readbacks I believe this is an unprofessional attitude. Callback conversation with reporter revealed the following information: reporter has not returned to phl since his incidence. In discussions with other pilots who transient phl, the reporter alleges that they also have had similar occurrences. The reporter advised that he believes that since 'controllers don't have to correct readbacks anymore', he must make absolutely sure that clrncs are correctly understood.

Original NASA ASRS Text

Title: ACR CAPT CHALLENGES PHL APCH CTLR NUMEROUS TIMES TO VERIFY CLRNC.

Narrative: PHL ARPT-WE RECEIVED AN APCH CLRNC THAT WAS PARTIALLY BLOCKED BY ANOTHER ACFT RADIO CALL. WE READBACK THE CLRNC WITH 'CONFIRM'. CTLR DID NOT RESPOND, SO WE ASKED HIM TO REPEAT THE CLRNC AGAIN, NO RESPONSE. WE ASKED 'PLEASE CONFIRM' WITH OUR CALL SIGN AND THE CLRNC WE BELIEVED TO HAVE RECEIVED. THE CTLR RESPONDED WITH 'YES,' VERY LOUDLY AND NOTHING ELSE. A FEW SECONDS LATER, HE TOLD US TO CONTACT TWR AND WE COMPLETED THE FLT UNEVENTFULLY. THE ARPT WAS VERY BUSY, BUT WITHOUT CTLR RESPONSIBILITY TO CORRECT READBACKS I BELIEVE THIS IS AN UNPROFESSIONAL ATTITUDE. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR HAS NOT RETURNED TO PHL SINCE HIS INCIDENCE. IN DISCUSSIONS WITH OTHER PLTS WHO TRANSIENT PHL, THE RPTR ALLEGES THAT THEY ALSO HAVE HAD SIMILAR OCCURRENCES. THE RPTR ADVISED THAT HE BELIEVES THAT SINCE 'CTLRS DON'T HAVE TO CORRECT READBACKS ANYMORE', HE MUST MAKE ABSOLUTELY SURE THAT CLRNCS ARE CORRECTLY UNDERSTOOD.

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.