Aircraft taxied onto runway without tower clearance.

Attributes
ACN	302860
Time
Date	199504
Day	Wed
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : phl
State Reference	PA
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	general aviation : corporate
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Operating Under FAR Part	Part 91
Flight Phase	ground other : taxi
Flight Plan	IFR
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : private pilot : instrument
Experience	flight time last 90 days : 30 flight time total : 600 flight time type : 300
ASRS Report	302860
Person 2
Affiliation	government : faa
Function	controller : local
Qualification	controller : non radar
Events
Anomaly	non adherence : clearance non adherence : far other anomaly other
Independent Detector	other controllera other flight crewa
Resolutory Action	flight crew : returned to intended course or assigned course flight crew : overcame equipment problem
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

On preparing to depart phl, ground cleared me to runway 27L, and sequenced behind beech 1900 following citation, then gave me tower frequency 133.1. I dialed in incorrect tower frequency, and after being unable to communication with tower, followed my sequenced clearance, and announced to ground my intentions. Ground then redirected me to tower. By this time I had positioned on runway 27L for departure. I contacted tower on the correct frequency, who inquired if I had heard their previous communication. I replied that I had not with no explanation. The tower controller then admonished me, correctly, for the incursion. The problem was caused by my not dialing the correct tower frequency, due to concentration on departure sequence, and then not checking it when no communication was heard. This is corrected by allowing one aspect of the flight operation (in this case departure sequence) overshadow other operations.

Original NASA ASRS Text

Title: ACFT TAXIED ONTO RWY WITHOUT TWR CLRNC.

Narrative: ON PREPARING TO DEPART PHL, GND CLRED ME TO RWY 27L, AND SEQUENCED BEHIND BEECH 1900 FOLLOWING CITATION, THEN GAVE ME TWR FREQ 133.1. I DIALED IN INCORRECT TWR FREQ, AND AFTER BEING UNABLE TO COM WITH TWR, FOLLOWED MY SEQUENCED CLRNC, AND ANNOUNCED TO GND MY INTENTIONS. GND THEN REDIRECTED ME TO TWR. BY THIS TIME I HAD POSITIONED ON RWY 27L FOR DEP. I CONTACTED TWR ON THE CORRECT FREQ, WHO INQUIRED IF I HAD HEARD THEIR PREVIOUS COM. I REPLIED THAT I HAD NOT WITH NO EXPLANATION. THE TWR CTLR THEN ADMONISHED ME, CORRECTLY, FOR THE INCURSION. THE PROB WAS CAUSED BY MY NOT DIALING THE CORRECT TWR FREQ, DUE TO CONCENTRATION ON DEP SEQUENCE, AND THEN NOT CHKING IT WHEN NO COM WAS HEARD. THIS IS CORRECTED BY ALLOWING ONE ASPECT OF THE FLT OP (IN THIS CASE DEP SEQUENCE) OVERSHADOW OTHER OPS.

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.