Narrative:

After experiencing a 1:30 delay receiving my release (die to traffic saturation) out of N67, I was issued and read back a release time of XX43 with a void time of XX46. I was issued this release at XX41. Due to the usual poor reception of the phl clearance rco frequency of 118.55 at N67, I had to get my release on the pay phone. I had prepared the aircraft for departure, so I would be able to depart as soon as I received a release time. My takeoff time was XX44, leaving 2 mins to spare on the void time of XX46. After departure I contacted phl approach on the assigned frequency of 126.85, and was advised I had missed my void time of 17:43. I informed the approach controller that I was issued a release time of XX43, a void time of XX46, and departed at XX44. The controller disputed this fact, and I decided, due to the amount of frequency congestion, not to continue the dispute on the radio. Contributing factors: 1) very(!!) poor rco for phl approach at N67. I have reported this problem several times, and have ignored the problem even more times. The inability to communicate with phl clearance through the rco at N67 has happened to me in several different aircraft over the last few yrs--not just this aircraft. This would lead me to believe it is not the aircraft's equipment, but rather the ground-based equipment. 2) lack of desperately needed additional personnel to properly coordinate efficient flow of traffic. (I feel the subject facility is doing as well as it can given the limited resources and manpwr provided by the administration.) suggestions: 1) fix the phl clearance delivery rco at N67 (this has been functionally obsolete for several yrs). 2) add more experienced personnel to cope with the increased traffic load in the phl area.

Related reports:

Google
 

Original NASA ASRS Text

Title: PLT AND CTLR DISPUTE VALID AND VOID TIE FOR IFR DEP. REPORTER CLAIMS REMOTE COM FAC AT N67 IS UNUSABLE.

Narrative: AFTER EXPERIENCING A 1:30 DELAY RECEIVING MY RELEASE (DIE TO TFC SATURATION) OUT OF N67, I WAS ISSUED AND READ BACK A RELEASE TIME OF XX43 WITH A VOID TIME OF XX46. I WAS ISSUED THIS RELEASE AT XX41. DUE TO THE USUAL POOR RECEPTION OF THE PHL CLRNC RCO FREQ OF 118.55 AT N67, I HAD TO GET MY RELEASE ON THE PAY PHONE. I HAD PREPARED THE ACFT FOR DEP, SO I WOULD BE ABLE TO DEPART AS SOON AS I RECEIVED A RELEASE TIME. MY TKOF TIME WAS XX44, LEAVING 2 MINS TO SPARE ON THE VOID TIME OF XX46. AFTER DEP I CONTACTED PHL APCH ON THE ASSIGNED FREQ OF 126.85, AND WAS ADVISED I HAD MISSED MY VOID TIME OF 17:43. I INFORMED THE APCH CTLR THAT I WAS ISSUED A RELEASE TIME OF XX43, A VOID TIME OF XX46, AND DEPARTED AT XX44. THE CTLR DISPUTED THIS FACT, AND I DECIDED, DUE TO THE AMOUNT OF FREQ CONGESTION, NOT TO CONTINUE THE DISPUTE ON THE RADIO. CONTRIBUTING FACTORS: 1) VERY(!!) POOR RCO FOR PHL APCH AT N67. I HAVE RPTED THIS PROB SEVERAL TIMES, AND HAVE IGNORED THE PROB EVEN MORE TIMES. THE INABILITY TO COMMUNICATE WITH PHL CLRNC THROUGH THE RCO AT N67 HAS HAPPENED TO ME IN SEVERAL DIFFERENT ACFT OVER THE LAST FEW YRS--NOT JUST THIS ACFT. THIS WOULD LEAD ME TO BELIEVE IT IS NOT THE ACFT'S EQUIP, BUT RATHER THE GND-BASED EQUIP. 2) LACK OF DESPERATELY NEEDED ADDITIONAL PERSONNEL TO PROPERLY COORDINATE EFFICIENT FLOW OF TFC. (I FEEL THE SUBJECT FAC IS DOING AS WELL AS IT CAN GIVEN THE LIMITED RESOURCES AND MANPWR PROVIDED BY THE ADMINISTRATION.) SUGGESTIONS: 1) FIX THE PHL CLRNC DELIVERY RCO AT N67 (THIS HAS BEEN FUNCTIONALLY OBSOLETE FOR SEVERAL YRS). 2) ADD MORE EXPERIENCED PERSONNEL TO COPE WITH THE INCREASED TFC LOAD IN THE PHL AREA.

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.