Narrative:

I was doing pattern work at jyo (under a sfra flight plan and squawk code) with another pilot on board. Calm winds (windsock slightly favored 17) and lots of other traffic in the area (total of eight planes in traffic pattern; in the run-up area; or taxiing to depart) dictated using runway 17. Prior to departure; we listened on the CTAF frequency for general situational awareness and cleared the downwind; base; final and runway prior to announcing our departure and rolling onto the runway. I performed a short-field take off from runway 17. As I lowered the nose after clearing the theoretical obstacle; we (both pilots) saw a plane ahead of us and above us. We quickly realized that the plane was descending into us on short final. We side-slipped to the right and continued climbing. I made a call on CTAF that we were side-stepping to the right of runway 17 for the arriving traffic and that we would continue our climb to a crosswind turn. The other plane did not respond. A few seconds later; another plane on the ground radioed that he had not heard the inbound aircraft make any calls (we had not either). The other aircraft never changed its flight path and never seemed aware that he was utilizing a runway opposite to all other traffic. Without an evasive maneuver; it is not clear whether we would have avoided the descending aircraft. We may have been above him by the time we crossed; we're not sure. The aircraft landed long and taxied all to the end of runway 35; departing the runway into the busy run-up area of runway 17; causing further confusion. We saw this as we turned crosswind and downwind. We were not able to ascertain an exact aircraft type. We know it was a twin; probably a beech; we think perhaps a baron.

Google
 

Original NASA ASRS Text

Title: A pilot departed JYO Runway 17 and at 500 FT took evasive action when a light twin entered Runway 35 final without any CTAF calls. The aircraft missed by 100 FT horizontally and vertically.

Narrative: I was doing pattern work at JYO (under a SFRA flight plan and squawk code) with another pilot on board. Calm winds (windsock slightly favored 17) and lots of other traffic in the area (total of eight planes in traffic pattern; in the run-up area; or taxiing to depart) dictated using Runway 17. Prior to departure; we listened on the CTAF frequency for general situational awareness and cleared the downwind; base; final and runway prior to announcing our departure and rolling onto the runway. I performed a short-field take off from Runway 17. As I lowered the nose after clearing the theoretical obstacle; we (both pilots) saw a plane ahead of us and above us. We quickly realized that the plane was descending into us on short final. We side-slipped to the right and continued climbing. I made a call on CTAF that we were side-stepping to the right of Runway 17 for the arriving traffic and that we would continue our climb to a crosswind turn. The other plane did not respond. A few seconds later; another plane on the ground radioed that he had not heard the inbound aircraft make any calls (we had not either). The other aircraft never changed its flight path and never seemed aware that he was utilizing a runway opposite to all other traffic. Without an evasive maneuver; it is not clear whether we would have avoided the descending aircraft. We may have been above him by the time we crossed; we're not sure. The aircraft landed long and taxied all to the end of Runway 35; departing the runway into the busy run-up area of Runway 17; causing further confusion. We saw this as we turned crosswind and downwind. We were not able to ascertain an exact aircraft type. We know it was a twin; probably a Beech; we think perhaps a Baron.

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.