Small transport gives TA's on wrong unicom frequency and has conflict with landing traffic.

Attributes
ACN	451504
Time
Date	199910
Day	Fri
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : fci.airport
State Reference	VA
Altitude	agl single value : 100
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	other
Make Model Name	Military
Operating Under FAR Part	Part 91
Flight Phase	climbout : initial climbout : takeoff
Route In Use	departure : vfr
Flight Plan	IFR
Aircraft 2
Operator	general aviation : personal
Make Model Name	Amateur (Home) Built
Flight Phase	descent : approach descent : vacating altitude
Route In Use	approach : straight in arrival : vfr
Person 1
Affiliation	government : military
Function	flight crew : single pilot
Qualification	pilot : military
Experience	flight time last 90 days : 120 flight time total : 1314
ASRS Report	451504
Person 2
Affiliation	other
Function	flight crew : single pilot
Qualification	pilot : private
Events
Anomaly	conflict : airborne critical non adherence : far non adherence : published procedure
Independent Detector	other flight crewa other flight crewb
Resolutory Action	flight crew : exited adverse environment flight crew : took evasive action
Supplementary
Problem Areas	Flight Crew Human Performance Environmental Factor
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

On oct/xa/99 at approximately AC40, richmond, va, I departed from chesterfield airport. Chesterfield airport has no control tower and is an uncontrolled airfield. I had made 4 radio calls on unicom frequency, announcing my departure on runway 33 from chesterfield. As I got my IFR clearance from richmond clearance delivery on frequency 124.6, they advised me of an approaching aircraft to runway 15 at chesterfield. I then went back to unicom frequency and announced that I was departing runway 33. The winds that morning were calm and slightly favored runway 33. I looked downwind and towards the runway and saw no traffic. I started my takeoff roll. I got airborne about 100 ft and then saw the approaching aircraft coming to runway 15. I made a clearing turn to the right and was well clear. The approaching aircraft discontinued his landing approach and pulled up from his approach to the runway and made a right turn towards the downwind side. I discovered later that I had made my unicom advisory calls on frequency 123.00 and not 123.05.

Original NASA ASRS Text

Title: SMT GIVES TA'S ON WRONG UNICOM FREQ AND HAS CONFLICT WITH LNDG TFC.

Narrative: ON OCT/XA/99 AT APPROX AC40, RICHMOND, VA, I DEPARTED FROM CHESTERFIELD ARPT. CHESTERFIELD ARPT HAS NO CTL TWR AND IS AN UNCTLED AIRFIELD. I HAD MADE 4 RADIO CALLS ON UNICOM FREQ, ANNOUNCING MY DEP ON RWY 33 FROM CHESTERFIELD. AS I GOT MY IFR CLRNC FROM RICHMOND CLRNC DELIVERY ON FREQ 124.6, THEY ADVISED ME OF AN APCHING ACFT TO RWY 15 AT CHESTERFIELD. I THEN WENT BACK TO UNICOM FREQ AND ANNOUNCED THAT I WAS DEPARTING RWY 33. THE WINDS THAT MORNING WERE CALM AND SLIGHTLY FAVORED RWY 33. I LOOKED DOWNWIND AND TOWARDS THE RWY AND SAW NO TFC. I STARTED MY TKOF ROLL. I GOT AIRBORNE ABOUT 100 FT AND THEN SAW THE APCHING ACFT COMING TO RWY 15. I MADE A CLRING TURN TO THE R AND WAS WELL CLR. THE APCHING ACFT DISCONTINUED HIS LNDG APCH AND PULLED UP FROM HIS APCH TO THE RWY AND MADE A R TURN TOWARDS THE DOWNWIND SIDE. I DISCOVERED LATER THAT I HAD MADE MY UNICOM ADVISORY CALLS ON FREQ 123.00 AND NOT 123.05.

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.