Date: 201810
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: IMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Skylane 182/RG Turbo Skylane/RG
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Landing
ATC / advisory: CTAF ZZZ
Second aircraft: Dassault-Breguet Undifferentiated or Other Model
Aircraft component: VHF
Component problem: Improperly Operated
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Commercial
Human factors: Communication Breakdown; Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Conflict NMAC; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Other Person
When detected: Taxi
Result: Flight Crew Took Evasive Action
Contributing factors: Airport; Procedure; Human Factors
Primary problem: Procedure

Narrative: IMC to ZZZ. ZZZ reported wind slight from NE; acceptable ceiling; requested from ZZZ Approach VOR to circle to RWY XX. Airport in site at VOR (7 miles). Set CTAF as backup on radios 1 and 2 and remained with Approach on Radio 1 until close to the field. Cancelled IFR; squawked 1200; switched radio 1 to CTAF and announced intent to cross midfield; enter downwind for RWY XX and land. No response; no apparent activity at the airport; wind sock favorable; announced downwind; base and final. Normal visual landing. Partway through the rollout I heard a noise that sounded like an aluminum bang on the left side. I visually checked left wing and all looked OK. Flaps were down and fine. I taxied to the FBO and the line guy mentioned he noticed us close as that Falcon took off. The sound I heard was apparently my left flap banging within its range of movement from the thrust of the jet crossing close above.In the FBO; they said they heard the Falcon make his departure contact announcement to ATC but was still on the clearance frequency; and that he sounded 'as cool as a cucumber'.My primary error is clear: It turns out I had set radio 2 backup correctly but had set radio 1 backup to [incorrect frequency]. No one would have heard my intent and position announcements. This resulted in a jet believing he was free to take off on RWY XY; and a near collision at the intersection. My error nearly led to the death of at least two of us. I also should not have cancelled IFR as I entered the pattern; since visibility down and horizontal were fine; I was not sufficiently below the broken layer above to qualify as VMC conditions.There are two potential contributing factors; although my error is the cause. 1: If the Falcon was given his clearance to take off; wouldn't he have been advised that there was another aircraft inbound or in the vicinity? 2: If I HAD been on the correct CTAF frequency; would the Falcon have heard my calls since neither of us were heard on the FBO's UNICOM radio; but he was heard on the clearance frequency that they apparently monitor?The lessons I take away from this incident are:1. Double check tuned frequencies.2. Make radio contact at the intended landing airport if there is no other activity on the frequency; even if just a radio check on UNICOM.3. If flying any approach other than in clear VFR conditions; DO NOT cancel IFR until either on final or on the ground.These lessons are now seared into my memory. I also thankful for the rapid response of the Falcon pilot; who I assume pulled up more quickly than normal; upon seeing me come in.




Synopsis: A Cessna 182 pilot reported that while landing at a non-towered airport another aircraft was taking off on a crossing runway.