Wrong runway approach by a military pilot creates a potential conflict with opposite direction depar...

Attributes
ACN	232661
Time
Date	199301
Day	Thu
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : sln
State Reference	KS
Altitude	agl bound lower : 300 agl bound upper : 300
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : sln tower : btr
Operator	other
Make Model Name	Fighter
Flight Phase	descent : approach landing : go around
Route In Use	approach : straight in approach : visual
Flight Plan	VFR
Aircraft 2
Operator	common carrier : air carrier
Make Model Name	Light Transport, Low Wing, 2 Turboprop Eng
Flight Phase	climbout : takeoff climbout : initial cruise other
Flight Plan	IFR
Person 1
Affiliation	government : military
Function	flight crew : single pilot
Qualification	pilot : military
Experience	flight time last 90 days : 180 flight time total : 8000
ASRS Report	232661
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	conflict : airborne less severe non adherence : clearance other anomaly other other spatial deviation
Independent Detector	other controllera other flight crewa
Resolutory Action	flight crew : took evasive action flight crew : exited adverse environment other
Consequence	Other
Miss Distance	horizontal : 6000 vertical : 100
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

There was a misunderstanding between pilot and tower controller as to which runway I was cleared to for visual/simulated emergency approach. Upon review of cockpit video/audio tape, I initiated an approach to runway 17 while cleared to runway 12. However, I read back 'cleared for visual approach' and did not state either runway on readback. The controller did not challenge my response. Approximately 1/2 mi north of runway 17, I noticed a turboprop commuter airborne northbound on runway 35 in a right turn to the east. I initiated a go around and cleared the runway to the west prior to the approach end of runway 17. I was never within 1 mi of departing aircraft. I understand that the commuter possibly filed a hatr, however, I did not feel that a significant hazard existed. I was communicating with the tower via UHF and the turboprop was on VHF, therefore, I could not hear his transmission and earlier in the approach was told to standby by the tower. I feel that congested frequency and multiple VFR aircraft along with simulcast VHF/UHF contributed to the incident.

Original NASA ASRS Text

Title: WRONG RWY APCH BY A MIL PLT CREATES A POTENTIAL CONFLICT WITH OPPOSITE DIRECTION DEP TFC.

Narrative: THERE WAS A MISUNDERSTANDING BTWN PLT AND TWR CTLR AS TO WHICH RWY I WAS CLRED TO FOR VISUAL/SIMULATED EMER APCH. UPON REVIEW OF COCKPIT VIDEO/AUDIO TAPE, I INITIATED AN APCH TO RWY 17 WHILE CLRED TO RWY 12. HOWEVER, I READ BACK 'CLRED FOR VISUAL APCH' AND DID NOT STATE EITHER RWY ON READBACK. THE CTLR DID NOT CHALLENGE MY RESPONSE. APPROX 1/2 MI N OF RWY 17, I NOTICED A TURBOPROP COMMUTER AIRBORNE NBOUND ON RWY 35 IN A R TURN TO THE E. I INITIATED A GAR AND CLRED THE RWY TO THE W PRIOR TO THE APCH END OF RWY 17. I WAS NEVER WITHIN 1 MI OF DEPARTING ACFT. I UNDERSTAND THAT THE COMMUTER POSSIBLY FILED A HATR, HOWEVER, I DID NOT FEEL THAT A SIGNIFICANT HAZARD EXISTED. I WAS COMMUNICATING WITH THE TWR VIA UHF AND THE TURBOPROP WAS ON VHF, THEREFORE, I COULD NOT HEAR HIS XMISSION AND EARLIER IN THE APCH WAS TOLD TO STANDBY BY THE TWR. I FEEL THAT CONGESTED FREQ AND MULTIPLE VFR ACFT ALONG WITH SIMULCAST VHF/UHF CONTRIBUTED TO THE INCIDENT.

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.

Wrong runway approach by a military pilot creates a potential conflict with opposite direction departure traffic.