Narrative:

We taxied normally to the departure end of the runway and held short of the runway to complete the engine run up and pre-take off checks. We waited for a sel aircraft approaching the runway to land and observed the aircraft clear the runway. The landing pilot announced his positions while in the pattern as well as upon clearing the runway on the unicom frequency. We visually scanned the pattern for traffic and did not see any other aircraft and did not hear any other radio calls. We announced our intention to depart on the runway on the unicom frequency. We then taxied into position and began the take off roll. Prior to attaining rotation speed we observed oncoming landing traffic (large MEL) on final to land on the opposite end of the runway. We immediately aborted the take off; moved to the extreme right side of the runway and cleared the runway at the next taxiway. The landing traffic continued its landing uneventfully. No radio call was heard from the landing aircraft at any time including as it exited the runway. The aircraft were never close to colliding. Once the runway environment was clear we taxied back and departed normally on the runway. We believe that the landing aircraft conducted a straight in approach against opposing traffic. We did not hear any radio calls from that aircraft. It is possible that the landing aircraft was using the wrong unicom frequency as the frequency had been changed within the previous 4 days.

Google
 

Original NASA ASRS Text

Title: An experimental taking off on the runway at an uncontrolled airport had to give way to a large multi engine aircraft landing the opposite direction. The other aircraft made no position calls on the UNICOM frequency which had been changed only a few days prior to the incident.

Narrative: We taxied normally to the departure end of the runway and held short of the runway to complete the engine run up and pre-take off checks. We waited for a SEL aircraft approaching the runway to land and observed the aircraft clear the runway. The landing pilot announced his positions while in the pattern as well as upon clearing the runway on the UNICOM frequency. We visually scanned the pattern for traffic and did not see any other aircraft and did not hear any other radio calls. We announced our intention to depart on the runway on the UNICOM frequency. We then taxied into position and began the take off roll. Prior to attaining rotation speed we observed oncoming landing traffic (large MEL) on final to land on the opposite end of the runway. We immediately aborted the take off; moved to the extreme right side of the runway and cleared the runway at the next taxiway. The landing traffic continued its landing uneventfully. No radio call was heard from the landing aircraft at any time including as it exited the runway. The aircraft were never close to colliding. Once the runway environment was clear we taxied back and departed normally on the runway. We believe that the landing aircraft conducted a straight in approach against opposing traffic. We did not hear any radio calls from that aircraft. It is possible that the landing aircraft was using the wrong UNICOM frequency as the frequency had been changed within the previous 4 days.

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