PC12 pilot experiences near midair collision with another aircraft at an uncontrolled airport. Later...

Attributes
ACN	742833
Time
Date	200706
Local Time Of Day	0601 To 1200
Place
State Reference	UT
Altitude	agl single value : 1500
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : charter
Make Model Name	PC-12
Operating Under FAR Part	Part 135
Flight Phase	descent : approach
Route In Use	approach : visual
Flight Plan	IFR
Aircraft 2
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Flight Phase	climbout : initial
Person 1
Affiliation	company : charter
Function	flight crew : single pilot
Qualification	pilot : multi engine pilot : instrument pilot : commercial pilot : cfi pilot : atp
Experience	flight time last 90 days : 60 flight time total : 8000 flight time type : 300
ASRS Report	742833
Events
Anomaly	conflict : nmac non adherence : published procedure
Independent Detector	other flight crewa
Resolutory Action	none taken : detected after the fact
Miss Distance	horizontal : 200 vertical : 200
Supplementary
Problem Areas	Flight Crew Human Performance Airport Airspace Structure
Primary Problem	Flight Crew Human Performance

Narrative:

I was rolling out on a 2 mi final approach to runway 16 at bmc; when the TAS alerted; just as I saw a twin engine aircraft approaching nearly head on. I was not sure if it had taken off on runway 34 at bmc; or had just over-flown it. The aircraft passed off my left wing; climbing. I had announced my position several times inbound to the airport; after canceling my IFR clearance about 20 mi out; but heard no other radio traffic on CTAF for bmc; other than a helicopter; but I could not determine which airport it was at. During rollout; I heard a radio call to a 'malibu' landing at bmc on runway 16; apparently from the twin I had seen; asking if it was on the right frequency and if it had seen the twin. I thought it might have been for the pilatus I was flying. I rechked my radio frequency and found that I had dialed in 123.00 for CTAF; instead of the published 123.05. Consequently; no one at bmc had heard my radio calls; nor had I heard theirs. Big error on my part; which could have resulted in disaster. The TAS warning was a good heads up. Neither aircraft took evasive action. I will certainly take pains to double/triple check radio frequencys in the future.

Original NASA ASRS Text

Title: PC12 PLT EXPERIENCES NMAC WITH ANOTHER ACFT AT AN UNCONTROLLED ARPT. LATER DISCOVERS INCORRECT CTAF FREQUENCY TUNED.

Narrative: I WAS ROLLING OUT ON A 2 MI FINAL APCH TO RWY 16 AT BMC; WHEN THE TAS ALERTED; JUST AS I SAW A TWIN ENG ACFT APCHING NEARLY HEAD ON. I WAS NOT SURE IF IT HAD TAKEN OFF ON RWY 34 AT BMC; OR HAD JUST OVER-FLOWN IT. THE ACFT PASSED OFF MY L WING; CLBING. I HAD ANNOUNCED MY POS SEVERAL TIMES INBOUND TO THE ARPT; AFTER CANCELING MY IFR CLRNC ABOUT 20 MI OUT; BUT HEARD NO OTHER RADIO TFC ON CTAF FOR BMC; OTHER THAN A HELI; BUT I COULD NOT DETERMINE WHICH ARPT IT WAS AT. DURING ROLLOUT; I HEARD A RADIO CALL TO A 'MALIBU' LNDG AT BMC ON RWY 16; APPARENTLY FROM THE TWIN I HAD SEEN; ASKING IF IT WAS ON THE RIGHT FREQ AND IF IT HAD SEEN THE TWIN. I THOUGHT IT MIGHT HAVE BEEN FOR THE PILATUS I WAS FLYING. I RECHKED MY RADIO FREQ AND FOUND THAT I HAD DIALED IN 123.00 FOR CTAF; INSTEAD OF THE PUBLISHED 123.05. CONSEQUENTLY; NO ONE AT BMC HAD HEARD MY RADIO CALLS; NOR HAD I HEARD THEIRS. BIG ERROR ON MY PART; WHICH COULD HAVE RESULTED IN DISASTER. THE TAS WARNING WAS A GOOD HEADS UP. NEITHER ACFT TOOK EVASIVE ACTION. I WILL CERTAINLY TAKE PAINS TO DOUBLE/TRIPLE CHK RADIO FREQS IN THE FUTURE.

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

PC12 pilot experiences near midair collision with another aircraft at an uncontrolled airport. Later discovers incorrect CTAF frequency tuned.