A C-172 departing a remote airfield suffered an near midair collision with a commercial fixed wing a...

Narrative:

I announced my departure from a remote airport on CTAF; stating runway 07 and departing to the east. I then took off and maintained runway heading as I climbed out. There is a VOR near the river on this heading approximately 3 miles east of the airport. At about 1;500 MSL approaching the VOR I had just changed over to the 'common' frequency along the river when I noticed a commercial air carrier twin in front and slightly below; heading directly at me. I turned slightly to the right and increased pitch slightly from climb so I could maintain visual contact with the approaching aircraft. It passed close enough that I could clearly see the pilots. The aircraft did not appear to take any evasive measures and continued on its straight descending attitude.first; I expect the traffic was on an IFR flight plan and the pilots may not have heard me announce my taxi or departure calls (same 123.0 frequency) from the airport. I think they were monitoring or contacting center announcing their arrival and therefore not monitoring the airport frequency. There is very limited cell phone coverage at this remote airfield and it is possible they were using their radios while still in contact with center to close their flight plan. Second; because the winds were calm; the aircraft was making a direct approach to runway 25 as I was making a direct departure from runway 07 (same runway; opposite direction). Third; I was approaching the VOR and near the river and I may have changed frequencies too soon. I heard no response or other traffic at anytime from taxi to departure so I did not expect other aircraft in the airport area during my departure. To prevent a repeat of this incident I will not maintain runway heading for so long after departure. I will fly an off-set heading ensuring I am not flying towards an aircraft making a straight in approach. Also; I would strongly encourage airport information to direct arriving aircraft to remain north of the river and departing aircraft to fly south of the river. Lastly; I will be extra aware when flying near a VOR and will better monitor two frequencies when appropriate.

Original NASA ASRS Text

Title: A C-172 departing a remote airfield suffered an NMAC with a commercial fixed wing aircraft inbound; opposite direction to the same runway.

Narrative: I announced my departure from a remote airport on CTAF; stating Runway 07 and departing to the east. I then took off and maintained runway heading as I climbed out. There is a VOR near the river on this heading approximately 3 miles east of the airport. At about 1;500 MSL approaching the VOR I had just changed over to the 'common' frequency along the river when I noticed a Commercial Air Carrier twin in front and slightly below; heading directly at me. I turned slightly to the right and increased pitch slightly from climb so I could maintain visual contact with the approaching aircraft. It passed close enough that I could clearly see the pilots. The aircraft did not appear to take any evasive measures and continued on its straight descending attitude.First; I expect the traffic was on an IFR flight plan and the pilots may not have heard me announce my taxi or departure calls (same 123.0 frequency) from the airport. I think they were monitoring or contacting Center announcing their arrival and therefore not monitoring the airport frequency. There is very limited cell phone coverage at this remote airfield and it is possible they were using their radios while still in contact with Center to close their flight plan. Second; because the winds were calm; the aircraft was making a direct approach to Runway 25 as I was making a direct departure from Runway 07 (same runway; opposite direction). Third; I was approaching the VOR and near the river and I may have changed frequencies too soon. I heard no response or other traffic at anytime from taxi to departure so I did not expect other aircraft in the airport area during my departure. To prevent a repeat of this incident I will not maintain runway heading for so long after departure. I will fly an off-set heading ensuring I am not flying towards an aircraft making a straight in approach. Also; I would strongly encourage airport information to direct arriving aircraft to remain north of the river and departing aircraft to fly south of the river. Lastly; I will be extra aware when flying near a VOR and will better monitor two frequencies when appropriate.

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

Attributes
ACN	1085673
Time
Date	201305
Local Time Of Day	1201-1800
Place
Locale Reference	ZZZ.Airport
State Reference	US
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	Skyhawk 172/Cutlass 172
Operating Under FAR Part	Part 91
Flight Phase	Takeoff
Flight Plan	VFR
Aircraft 2
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Operating Under FAR Part	Part 135
Flight Phase	Initial Approach
Flight Plan	IFR
Person 1
Function	Pilot Flying Instructor
Qualification	Flight Crew Commercial Flight Crew Flight Instructor Flight Crew Instrument
Experience	Flight Crew Last 90 Days 30 Flight Crew Total 1275 Flight Crew Type 1000
Events
Anomaly	Conflict NMAC
Miss Distance	Horizontal 100 Vertical 300

A C-172 departing a remote airfield suffered an near midair collision with a commercial fixed wing aircraft inbound; opposite direction to the same runway.