FAA inspector alleges a BE55 and a BE40 had an near midair collision.

Attributes
ACN	421427
Time
Date	199811
Day	Tue
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : mcb
State Reference	MS
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	general aviation : personal
Flight Phase	climbout : intermediate altitude
Route In Use	departure other
Flight Plan	None
Aircraft 2
Flight Phase	climbout : intermediate altitude
Route In Use	departure other
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : cfi pilot : commercial
Experience	flight time last 90 days : 100 flight time total : 2500 flight time type : 300
ASRS Report	421427
Person 2
Affiliation	Other
Function	flight crew : captain oversight : pic
Events
Anomaly	conflict : airborne less severe non adherence : far
Independent Detector	other other : unspecified
Resolutory Action	none taken : detected after the fact other
Consequence	faa : investigated
Supplementary
Air Traffic Incident	other

Narrative:

On dec/xa/98 I was contacted by an FAA agent who alleged that I had an near midair collision with a beech jet near mccomb, ms, on departure and that I used the wrong CTAF. I was also informed that I made a downwind takeoff on runway 15. Please note that the winds at this time were light and variable. Also note that this call from the FAA agent was the first time I heard of this alleged near midair collision. At this time, as well as all times I have plted any aircraft, I was vigilant in looking for any other aircraft and at no time on the date in question did I see any other aircraft nor did I come close to any other aircraft in the mccomb area. I departed runway 15 and I did make a r-hand turnout to the west. I was informed by the FAA agent that the mccomb airport has a new TA frequency and I was not aware of this fact. I did make 2 calls inbound to mccomb requesting TA's and announced downwind and final. On departure, I announced I was departing on runway 15 and also announced I was departing to the west. These announcements must have been on the frequency I thought was mccomb's having received no answer to my xmissions. I obtained the frequency information for mccomb from my GPS in which the data card is only 1 yr old and I have now been informed that mccomb changed their frequency about 7 months ago.

Original NASA ASRS Text

Title: FAA INSPECTOR ALLEGES A BE55 AND A BE40 HAD AN NMAC.

Narrative: ON DEC/XA/98 I WAS CONTACTED BY AN FAA AGENT WHO ALLEGED THAT I HAD AN NMAC WITH A BEECH JET NEAR MCCOMB, MS, ON DEP AND THAT I USED THE WRONG CTAF. I WAS ALSO INFORMED THAT I MADE A DOWNWIND TKOF ON RWY 15. PLEASE NOTE THAT THE WINDS AT THIS TIME WERE LIGHT AND VARIABLE. ALSO NOTE THAT THIS CALL FROM THE FAA AGENT WAS THE FIRST TIME I HEARD OF THIS ALLEGED NMAC. AT THIS TIME, AS WELL AS ALL TIMES I HAVE PLTED ANY ACFT, I WAS VIGILANT IN LOOKING FOR ANY OTHER ACFT AND AT NO TIME ON THE DATE IN QUESTION DID I SEE ANY OTHER ACFT NOR DID I COME CLOSE TO ANY OTHER ACFT IN THE MCCOMB AREA. I DEPARTED RWY 15 AND I DID MAKE A R-HAND TURNOUT TO THE W. I WAS INFORMED BY THE FAA AGENT THAT THE MCCOMB ARPT HAS A NEW TA FREQ AND I WAS NOT AWARE OF THIS FACT. I DID MAKE 2 CALLS INBOUND TO MCCOMB REQUESTING TA'S AND ANNOUNCED DOWNWIND AND FINAL. ON DEP, I ANNOUNCED I WAS DEPARTING ON RWY 15 AND ALSO ANNOUNCED I WAS DEPARTING TO THE W. THESE ANNOUNCEMENTS MUST HAVE BEEN ON THE FREQ I THOUGHT WAS MCCOMB'S HAVING RECEIVED NO ANSWER TO MY XMISSIONS. I OBTAINED THE FREQ INFO FOR MCCOMB FROM MY GPS IN WHICH THE DATA CARD IS ONLY 1 YR OLD AND I HAVE NOW BEEN INFORMED THAT MCCOMB CHANGED THEIR FREQ ABOUT 7 MONTHS AGO.

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.