PA34 pilot reported rejecting takeoff after observing unannounced traffic on short final landing on ...

Attributes
ACN	1466180
Time
Date	201707
Local Time Of Day	1201-1800
Place
Locale Reference	JYO.Airport
State Reference	VA
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	PA-34-200T Turbo Seneca II
Operating Under FAR Part	Part 91
Flight Phase	Takeoff
Route In Use	Vectors
Flight Plan	IFR
Aircraft 2
Make Model Name	Cirrus Aircraft Undifferentiated
Operating Under FAR Part	Part 91
Flight Phase	Final Approach
Person 1
Function	Single Pilot
Qualification	Flight Crew Air Transport Pilot (ATP) Flight Crew Flight Instructor Flight Crew Instrument Flight Crew Multiengine
Experience	Flight Crew Last 90 Days 25 Flight Crew Total 4000 Flight Crew Type 1200
Events
Anomaly	Conflict Ground Conflict Less Severe Deviation - Procedural Clearance Ground Incursion Runway
Miss Distance	Horizontal 3000 Vertical 0

Narrative:

Departing jyo. Part time tower closes in the afternoon. Called ground for clearance. Was informed tower was closing; runway 35 was in use and to get clearance from potomac approach. Announced taxi to runway 35 on unicom and taxied to run-up area. Switched frequencies and got IFR clearance. Was told there was inbound IFR traffic and that we were cleared to go as soon as they arrived. Traffic was on base for 35. They landed and we announced our departure for 35 on unicom and taxied out. As landing traffic cleared runway we started our takeoff roll. As we rolled I spotted landing lights on short final for runway 17. I aborted takeoff and stopped the plane well to the side of the runway. The approaching airplane; a cirrus; landed and taxied off the runway. We then departed on runway 35. I do not believe the cirrus ever saw us. We did not hear him call position or intentions on unicom. The wind favored runway 35 and that was the direction all traffic had been landing according to the tower before it closed. The runway is long and neither airplane was in jeopardy as the cirrus stopped in a short distance and exited the runway. But had I not seen them in the distance it could have been much closer.

Original NASA ASRS Text

Title: PA34 pilot reported rejecting takeoff after observing unannounced traffic on short final landing on the opposite direction runway.

Narrative: Departing JYO. Part time Tower closes in the afternoon. Called Ground for clearance. Was informed Tower was closing; Runway 35 was in use and to get clearance from Potomac Approach. Announced taxi to Runway 35 on Unicom and taxied to run-up area. Switched frequencies and got IFR clearance. Was told there was inbound IFR traffic and that we were cleared to go as soon as they arrived. Traffic was on base for 35. They landed and we announced our departure for 35 on Unicom and taxied out. As landing traffic cleared runway we started our takeoff roll. As we rolled I spotted landing lights on short final for Runway 17. I aborted takeoff and stopped the plane well to the side of the runway. The approaching airplane; a Cirrus; landed and taxied off the runway. We then departed on Runway 35. I do not believe the Cirrus ever saw us. We did not hear him call position or intentions on Unicom. The wind favored Runway 35 and that was the direction all traffic had been landing according to the Tower before it closed. The runway is long and neither airplane was in jeopardy as the Cirrus stopped in a short distance and exited the runway. But had I not seen them in the distance it could have been much closer.

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.