Beechjet 400 captain reported spotting unannounced traffic on short final lining up to land from the...

Narrative:

We were a beechjet 400A charter flight with 2 passengers out of statesville regional airport ready to start our taxi to runway 10. We made the call on CTAF 123.075 for our intentions to taxi to runway 10. We didn't hear any traffic on the frequency and we started the taxi to runway 10. Before we entered runway 10 we gave a call again on the same frequency saying our intentions to depart on that runway; we checked before we entered to the runway for any traffic and we didn't see any traffic and nobody [made] any reports either. We entered the runway and after our last checks for the takeoff; we started the takeoff roll and about 5 seconds later we identified traffic on short final for runway 28; we aborted the takeoff and expedited our exit off the runway. We did taxi back on the taxiway to take runway 10 again; we saw the [other aircraft] clearing the runway without any call at all. We did the same procedure and took off out of runway 10. The next day we flew back to statesville regional airport to drop off one of our passengers and were able to talk to the person who was in charge for line service. He talked to us what he witnessed the day of the incident I just described; and mentioned the same facts and airport activities. He also stated he was able to talk to the pilot of the [other aircraft] involved; saying he was giving a call on a frequency not published on the current charts but a frequency of 20 years ago; the pilot also mentioned that he never saw the beechjet on the runway or any other traffic on takeoff roll. I understand there is a lack of information gathered from the [other aircraft] pilot before flight as a result of a runway incursion and that could be prevented with the correct preparation for the flight; situational awareness improvement and traffic surveillance on runway selected for landing.

Original NASA ASRS Text

Title: Beechjet 400 Captain reported spotting unannounced traffic on short final lining up to land from the opposite direction on the runway which they had just started their takeoff roll. Takeoff was aborted.

Narrative: We were a Beechjet 400A charter flight with 2 passengers out of Statesville Regional Airport ready to start our taxi to runway 10. We made the call on CTAF 123.075 for our intentions to taxi to runway 10. We didn't hear any traffic on the frequency and we started the taxi to runway 10. Before we entered runway 10 we gave a call again on the same frequency saying our intentions to depart on that runway; we checked before we entered to the runway for any traffic and we didn't see any traffic and nobody [made] any reports either. We entered the runway and after our last checks for the takeoff; we started the takeoff roll and about 5 seconds later we identified traffic on short final for runway 28; we aborted the takeoff and expedited our exit off the runway. We did taxi back on the taxiway to take runway 10 again; we saw the [other aircraft] clearing the runway without any call at all. We did the same procedure and took off out of runway 10. The next day we flew back to Statesville Regional Airport to drop off one of our passengers and were able to talk to the person who was in charge for line service. He talked to us what he witnessed the day of the incident I just described; and mentioned the same facts and airport activities. He also stated he was able to talk to the Pilot of the [other aircraft] involved; saying he was giving a call on a frequency not published on the current charts but a frequency of 20 years ago; the Pilot also mentioned that he never saw the Beechjet on the runway or any other traffic on takeoff roll. I understand there is a lack of information gathered from the [other aircraft] Pilot before flight as a result of a runway incursion and that could be prevented with the correct preparation for the flight; situational awareness improvement and traffic surveillance on runway selected for landing.

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.

Attributes
ACN	1285007
Time
Date	201507
Local Time Of Day	1201-1800
Place
Locale Reference	SVH.Airport
State Reference	NC
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	Beechjet 400
Operating Under FAR Part	Part 135
Flight Phase	Takeoff
Flight Plan	IFR
Aircraft 2
Make Model Name	Small Aircraft
Operating Under FAR Part	Part 91
Flight Phase	Landing Final Approach
Person 1
Function	Captain
Qualification	Flight Crew Air Transport Pilot (ATP) Flight Crew Multiengine Flight Crew Instrument
Experience	Flight Crew Last 90 Days 120 Flight Crew Total 3850 Flight Crew Type 290
Events
Anomaly	Conflict Ground Conflict Less Severe Deviation - Procedural Published Material / Policy

Beechjet 400 captain reported spotting unannounced traffic on short final lining up to land from the opposite direction on the runway which they had just started their takeoff roll. Takeoff was aborted.