Narrative:

After departure from pne, I received frequency change approval to phl. During climb out I was handed off to 3 different controllers of phl before being handled by ATC, during which time I had converging traffic at 10 O'clock, appearing to be air carrier airlines in clean confign. I leveled off to avoid conflict. Shortly after I saw a smaller aircraft of no factor. My intentions were not to transit phl TCA but in anticipation of traffic I wanted advisories. The first controller could have at least informed me of a high workload. My practice is to monitor frequency and communication with the next controller to hear any possible traffic calls to any aircraft but I only had 1 communication radio during that flight. Also since pne control was not busy, maybe any communication between pne and phl would have helped avoid this problem.

Google
 

Original NASA ASRS Text

Title: REPORTER ACFT INADVERTENTLY ENTERED A TCA. WHILE ATTEMPTING TO ESTABLISH PROPER RADIO CONTACT REPORTER ACFT ALSO HAD A TRAFFIC CONFLICT WITH A LARGE ACR ACFT.

Narrative: AFTER DEP FROM PNE, I RECEIVED FREQ CHANGE APPROVAL TO PHL. DURING CLBOUT I WAS HANDED OFF TO 3 DIFFERENT CTLRS OF PHL BEFORE BEING HANDLED BY ATC, DURING WHICH TIME I HAD CONVERGING TFC AT 10 O'CLOCK, APPEARING TO BE ACR AIRLINES IN CLEAN CONFIGN. I LEVELED OFF TO AVOID CONFLICT. SHORTLY AFTER I SAW A SMALLER ACFT OF NO FACTOR. MY INTENTIONS WERE NOT TO TRANSIT PHL TCA BUT IN ANTICIPATION OF TFC I WANTED ADVISORIES. THE FIRST CTLR COULD HAVE AT LEAST INFORMED ME OF A HIGH WORKLOAD. MY PRACTICE IS TO MONITOR FREQ AND COM WITH THE NEXT CTLR TO HEAR ANY POSSIBLE TFC CALLS TO ANY ACFT BUT I ONLY HAD 1 COM RADIO DURING THAT FLT. ALSO SINCE PNE CTL WAS NOT BUSY, MAYBE ANY COM BTWN PNE AND PHL WOULD HAVE HELPED AVOID THIS PROB.

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