C182 pilot reported transmitting on incorrect CTAF frequency resulted in runway incursion and ground...

Attributes
ACN	1681937
Time
Date	201909
Local Time Of Day	0601-1200
Place
Locale Reference	ZZZ.Airport
State Reference	US
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	Skylane 182/RG Turbo Skylane/RG
Operating Under FAR Part	Part 91
Flight Phase	Takeoff
Route In Use	Direct
Flight Plan	IFR
Component
Aircraft Component	Air/Ground Communication
Person 1
Function	Single Pilot
Qualification	Flight Crew Flight Instructor Flight Crew Flight Engineer Flight Crew Air Transport Pilot (ATP) Flight Crew Instrument Flight Crew Multiengine
Experience	Flight Crew Last 90 Days 175 Flight Crew Total 8000 Flight Crew Type 150
Events
Anomaly	Conflict Ground Conflict Critical Deviation - Procedural Published Material / Policy Ground Incursion Runway
Miss Distance	Horizontal 8000 Vertical 100

Narrative:

I filed IFR from ZZZ to ZZZ1. Weather was VMC. Clear sky with unlimited visibility and a light direct crosswind of 6 knots. My plan was to depart ZZZ VFR and pick up my IFR clearance once airborne with approach control. I chose runway xx for departure for direction of flight. I self-announced my taxi plan (on what I thought was CTAF) and taxied to the hold line of runway xx where I performed my run-up and before takeoff checks. I hadn't heard any other traffic on frequency from the time I had cranked up.I self-announced I was taking runway xx for takeoff and a straight out departure; and proceeded to take the runway and push the power up for takeoff. This is when I noticed another cessna on short final for the opposite runway xy. I immediately aborted my takeoff and made a sharp left turn; promptly exiting the runway at the same taxiway I had entered from. The other cessna continued his landing uneventfully and taxied to park. I analyzed the situation once clear of the runway and found that I was a digit off when setting the CTAF frequency. I actually had set the unicom frequency instead of CTAF. I corrected the error and got a radio check; then proceeded without further issue.

Original NASA ASRS Text

Title: C182 pilot reported transmitting on incorrect CTAF frequency resulted in runway incursion and ground conflict with landing traffic.

Narrative: I filed IFR from ZZZ to ZZZ1. Weather was VMC. Clear sky with unlimited visibility and a light direct crosswind of 6 knots. My plan was to depart ZZZ VFR and pick up my IFR clearance once airborne with Approach Control. I chose Runway XX for departure for direction of flight. I self-announced my taxi plan (on what I thought was CTAF) and taxied to the hold line of Runway XX where I performed my run-up and before takeoff checks. I hadn't heard any other traffic on frequency from the time I had cranked up.I self-announced I was taking Runway XX for takeoff and a straight out departure; and proceeded to take the runway and push the power up for takeoff. This is when I noticed another Cessna on short final for the opposite Runway XY. I immediately aborted my takeoff and made a sharp left turn; promptly exiting the runway at the same taxiway I had entered from. The other Cessna continued his landing uneventfully and taxied to park. I analyzed the situation once clear of the runway and found that I was a digit off when setting the CTAF frequency. I actually had set the UNICOM frequency instead of CTAF. I corrected the error and got a radio check; then proceeded without further issue.

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