<< >> NASA ASRS Report 362450, March 1997

Private aircraft landed bjc and after circling the runway, contacted ground control on 121 pt 8. The trouble is, that is the frequency for another airport serving the same city. This other ground controller gave him taxi clearance which he accepted, thus taxiing without clearance.

Attributes
ACN	362450
Time
Date	199703
Day	Wed
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : bjc
State Reference	CO
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : apa
Operator	general aviation : personal
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 91
Flight Phase	ground other : taxi
Flight Plan	None
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : atp
Experience	flight time last 90 days : 50 flight time total : 15000 flight time type : 25
ASRS Report	362450
Person 2
Affiliation	government : faa
Function	controller : ground
Qualification	controller : non radar
Events
Anomaly	non adherence : far other anomaly other
Independent Detector	other flight crewa
Resolutory Action	none taken : detected after the fact
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Upon landing at bjc, took first turnoff and stopped short of parallel taxiway. Controller said contact ground on 121.8. I did that and asked for clearance to ramp (non controled area). Was given clearance to cross bjt, was told I was 'scratchy.' I confirmed clearance and proceeded into ramp area. Ground control was also noisy to use. After further thought I was given and used wrong ground frequency. 121.8 is ground control for apa across town many mi away. Would suggest a change of ground control frequencys in the denver area. Having 3 frequencys that are consecutive is prone to error. Currently using 121.7, 121.8, and 121.9 in this area.

Related reports:

• Air carrier contacted tower late, resulting in the controlle...
• An aircraft on an IFR approach to a non radar tower first co...
• PA28-161 aircraft checked NOTAMS for airport but after landi...
• A320 aircraft on STAR arrival FMGC inputs were checked, the ...
• MD80S aircraft in cruise received TCASII RA and flight crew ...
• Air carrier aircraft cleared ILS runway 35L maintain 180 KTS...

	Enter your search terms Submit search form
	Web www.37000feet.com

Original NASA ASRS Text

Title: PVT ACFT LANDED BJC AND AFTER CIRCLING THE RWY, CONTACTED GND CTL ON 121 PT 8. THE TROUBLE IS, THAT IS THE FREQ FOR ANOTHER ARPT SERVING THE SAME CITY. THIS OTHER GND CTLR GAVE HIM TAXI CLRNC WHICH HE ACCEPTED, THUS TAXIING WITHOUT CLRNC.

Narrative: UPON LNDG AT BJC, TOOK FIRST TURNOFF AND STOPPED SHORT OF PARALLEL TXWY. CTLR SAID CONTACT GND ON 121.8. I DID THAT AND ASKED FOR CLRNC TO RAMP (NON CTLED AREA). WAS GIVEN CLRNC TO CROSS BJT, WAS TOLD I WAS 'SCRATCHY.' I CONFIRMED CLRNC AND PROCEEDED INTO RAMP AREA. GND CTL WAS ALSO NOISY TO USE. AFTER FURTHER THOUGHT I WAS GIVEN AND USED WRONG GND FREQ. 121.8 IS GND CTL FOR APA ACROSS TOWN MANY MI AWAY. WOULD SUGGEST A CHANGE OF GND CTL FREQS IN THE DENVER AREA. HAVING 3 FREQS THAT ARE CONSECUTIVE IS PRONE TO ERROR. CURRENTLY USING 121.7, 121.8, AND 121.9 IN THIS AREA.

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.