A corporate pilot on the jyo RNAV/GPS 17 reported airborne conflicts with two aircraft which had dep...

Narrative:

Inbound to jyo on an IFR flight; we requested the RNAV/GPS 17 approach from potomac and were being vectored for it. Twenty miles north of the airport; I went off number one com [radio] and called unicom on number two com; reporting twenty north and asking for active runway at leesburg. The response was that the winds were 240 at 8 KTS. Nothing about active runway; so I advised that we would land [runway] 17. For the next ten miles; I monitored CTAF and ATC. I heard one aircraft announcing departing 17 and two separate aircraft announcing taxiing to runway 17. I also reported on unicom ten miles north on the GPS approach. Potomac cleared us for the approach and I had to turn number two radio off due to workload. At five miles out; we had the airport in sight and canceled IFR (maintaining squawk code as required). ATC took the cancellation and advised change to advisory frequency. He also advised before we switched that he had traffic 12 o'clock that appeared to have just departed [runway] 35. We thanked him and switched quickly to CTAF. I announced a three mile final runway 17; hoping to get a response. No one answered. In the next twenty seconds; a cessna passed off our left opposite direction and then a low wing single engine aircraft passed off our right; opposite direction and climbing. I keyed the microphone and said; 'say the active leesburg.' finally someone responded; saying that 35 was in use for departures. We broke off the landing and circled for 35. There were three aircraft waiting to depart. As much as I tried to communicate and find out traffic locations and active runway; leesburg is uncontrolled with only a unicom operator. As busy as the airport is; it either needs a full time aas service or a control tower. It would have been helpful as well if potomac approach had a clue that leesburg traffic was using [runway] 35 if he would have mentioned it to us..

Original NASA ASRS Text

Title: A corporate pilot on the JYO RNAV/GPS 17 reported airborne conflicts with two aircraft which had departed on Runway 35 but had not responded to CTAF traffic reports.

Narrative: Inbound to JYO on an IFR flight; we requested the RNAV/GPS 17 approach from Potomac and were being vectored for it. Twenty miles north of the airport; I went off number one com [radio] and called UNICOM on number two com; reporting twenty north and asking for active runway at Leesburg. The response was that the winds were 240 at 8 KTS. Nothing about active runway; so I advised that we would land [Runway] 17. For the next ten miles; I monitored CTAF and ATC. I heard one aircraft announcing departing 17 and two separate aircraft announcing taxiing to Runway 17. I also reported on UNICOM ten miles north on the GPS approach. Potomac cleared us for the Approach and I had to turn number two radio off due to workload. At five miles out; we had the airport in sight and canceled IFR (maintaining squawk code as required). ATC took the cancellation and advised change to advisory frequency. He also advised before we switched that he had traffic 12 o'clock that appeared to have just departed [Runway] 35. We thanked him and switched quickly to CTAF. I announced a three mile final Runway 17; hoping to get a response. No one answered. In the next twenty seconds; a Cessna passed off our left opposite direction and then a low wing single engine aircraft passed off our right; opposite direction and climbing. I keyed the microphone and said; 'Say the active Leesburg.' Finally someone responded; saying that 35 was in use for departures. We broke off the landing and circled for 35. There were three aircraft waiting to depart. As much as I tried to communicate and find out traffic locations and active runway; Leesburg is uncontrolled with only a UNICOM operator. As busy as the airport is; it either needs a full time AAS service or a Control Tower. It would have been helpful as well if Potomac Approach had a clue that Leesburg traffic was using [Runway] 35 if he would have mentioned it to us..

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.

Attributes
ACN	959885
Time
Date	201107
Local Time Of Day	1201-1800
Place
Locale Reference	JYO.Airport
State Reference	VA
Environment
Flight Conditions	VMC
Light	Dawn
Aircraft 1
Make Model Name	Small Transport Low Wing 2 Turboprop Eng
Operating Under FAR Part	Part 91
Flight Phase	Final Approach
Flight Plan	IFR
Aircraft 2
Make Model Name	Small Aircraft Low Wing 1 Eng Fixed Gear
Flight Phase	Initial Climb
Person 1
Function	Pilot Not Flying Captain
Qualification	Flight Crew Flight Instructor Flight Crew Flight Engineer Flight Crew Air Transport Pilot (ATP) Flight Crew Multiengine Flight Crew Instrument
Experience	Flight Crew Last 90 Days 120 Flight Crew Total 24100 Flight Crew Type 1960
Events
Anomaly	Conflict Airborne Conflict Deviation - Procedural Published Material / Policy
Miss Distance	Horizontal 500 Vertical 0

A corporate pilot on the jyo RNAV/GPS 17 reported airborne conflicts with two aircraft which had departed on runway 35 but had not responded to CTAF traffic reports.