37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 841302 |
Time | |
Date | 200906 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ROA.Airport |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Skyhawk 172/Cutlass 172 |
Flight Phase | Cruise |
Route In Use | Other prac area |
Flight Plan | None |
Person 1 | |
Function | Pilot Not Flying |
Qualification | Flight Crew Flight Instructor Flight Crew Instrument Flight Crew Multiengine Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 125 Flight Crew Total 6065 Flight Crew Type 400 |
Events | |
Anomaly | Conflict Airborne Conflict |
Miss Distance | Horizontal 5000 |
Narrative:
In an established roa practice area with a primary private pilot student instructing him in flight solely by reference to instruments and him 'under the hood'; we were squawking a discreet code. ATC called traffic at 1 o'clock and 3 miles same altitude; opposite direction. We observed the traffic at our 3 o'clock and about 2 miles and reported same to ATC. Traffic was then observed making a steep right hand turn; reversing direction. ATC then called traffic at my 6 o'clock and 1 mi. I immediately initiated a 90 left turn and moved to the other side of the practice area. A minute or so later; ATC called with an 'emergency traffic alert' at my 12 o'clock and 1 mi. I again initiated a 90 degree turn and observed the traffic again in a steep turn to my 6 o'clock position. I had already had the student remove his 'foggles' to help look for traffic. It was obvious to both of us that the traffic (same one) was deliberately 'dog-fighting' with us. I contacted roa approach and advised that I wished to immediately return to roa for landing and that it appeared that the traffic was 'dog-fighting' us. Roa attempted to reach the other aircraft with no result. (We were outside of roa class C; but in their airspace). The traffic (which was faster than our aircraft) followed us to the boundary of class C and broke off. We landed without incident. I don't know of anything I could have done differently; but; obviously; my student was quite rattled by the incident. I did get a good view of the aircraft's paint scheme and but didn't recognize it. I instruct 5-6 days a week; and this was my second 'near-miss' in two days; but this was my first ever-deliberate one!
Original NASA ASRS Text
Title: General aviation pilot providing instruction in locally accepted practice area near ROA reported conflict with another aircraft that was allegedly dog-fighting with the reporter.
Narrative: In an established ROA practice area with a primary private pilot student instructing him in flight solely by reference to instruments and him 'under the hood'; we were squawking a discreet code. ATC called traffic at 1 o'clock and 3 miles same altitude; opposite direction. We observed the traffic at our 3 o'clock and about 2 miles and reported same to ATC. Traffic was then observed making a steep right hand turn; reversing direction. ATC then called traffic at my 6 o'clock and 1 mi. I immediately initiated a 90 left turn and moved to the other side of the practice area. A minute or so later; ATC called with an 'Emergency Traffic Alert' at my 12 o'clock and 1 mi. I again initiated a 90 degree turn and observed the traffic again in a steep turn to my 6 o'clock position. I had already had the student remove his 'foggles' to help look for traffic. It was obvious to both of us that the traffic (same one) was deliberately 'dog-fighting' with us. I contacted ROA Approach and advised that I wished to immediately return to ROA for landing and that it appeared that the traffic was 'dog-fighting' us. ROA attempted to reach the other aircraft with no result. (We were outside of ROA Class C; but in their airspace). The traffic (which was faster than our aircraft) followed us to the boundary of Class C and broke off. We landed without incident. I don't know of anything I could have done differently; but; obviously; my student was quite rattled by the incident. I did get a good view of the aircraft's paint scheme and but didn't recognize it. I instruct 5-6 days a week; and this was my second 'near-miss' in two days; but this was my first ever-deliberate one!
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.