37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1554191 |
Time | |
Date | 201806 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | 54J.Airport |
State Reference | FL |
Environment | |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Skylane 182/RG Turbo Skylane/RG |
Operating Under FAR Part | Part 91 |
Flight Phase | Cruise |
Flight Plan | VFR |
Aircraft 2 | |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 91 |
Flight Phase | Descent |
Person 1 | |
Function | Single Pilot |
Qualification | Flight Crew Private Flight Crew Instrument |
Experience | Flight Crew Last 90 Days 7 Flight Crew Total 1870 Flight Crew Type 1200 |
Events | |
Anomaly | Conflict Airborne Conflict Inflight Event / Encounter Other / Unknown |
Narrative:
I flew today to practice VFR maneuvers; perform touch-and-goes; and maintain overall proficiency. I checked notams before flight; received a standard weather briefing from foreflight; and filed a VFR flight plan. To fly in the local area; all flight operations occur in the vicinity of several private use airports (without a CTAF frequency printed on the VFR sectional chart); [military airport] restricted airspace; multiple moas; military helicopter training flights; parachute jumping; and uav operations. These hazards occur routinely throughout the airspace; regardless of notams; and constant pilot vigilance is required. In addition; there has been a standing NOTAM for parachute jumping at a private airfield near my home airport.as I was flying north today towards an airport in the vicinity of the parachute jump airfield; I noticed a parachute jumper above and about 2 miles ahead of my flight path. I turned east to stay well clear of the jumper; and I continuously performed a visual scan for a potential jump plane; but saw no other aircraft. I also have ads-B in/out installed in my aircraft's panel; and no traffic was displayed preceding this event. After approximately another minute of elapsed flight time; a descending aircraft (along with its tail number) eventually appeared on my ads-B displays in close proximity to my aircraft. However; neither my tablet display nor my panel avionics annunciated an audible traffic conflict warning.this event reinforces the limitations of both visual see-and-avoid and ads-B traffic displays when non-collaborating aircraft are maneuvering near each other. As always; pre-flight planning; situational awareness; visual scanning; aviate/navigate/communicate priorities; and constant vigilance are paramount to overcome these limitations.
Original NASA ASRS Text
Title: C182 pilot reported an airborne conflict with a skydiver and the descending parachute jump plane.
Narrative: I flew today to practice VFR maneuvers; perform touch-and-goes; and maintain overall proficiency. I checked NOTAMs before flight; received a standard weather briefing from ForeFlight; and filed a VFR flight plan. To fly in the local area; all flight operations occur in the vicinity of several private use airports (without a CTAF frequency printed on the VFR sectional chart); [military airport] restricted airspace; multiple MOAs; military helicopter training flights; parachute jumping; and UAV operations. These hazards occur routinely throughout the airspace; regardless of NOTAMs; and constant pilot vigilance is required. In addition; there has been a standing NOTAM for parachute jumping at a private airfield near my home airport.As I was flying north today towards an airport in the vicinity of the parachute jump airfield; I noticed a parachute jumper above and about 2 miles ahead of my flight path. I turned east to stay well clear of the jumper; and I continuously performed a visual scan for a potential jump plane; but saw no other aircraft. I also have ADS-B in/out installed in my aircraft's panel; and no traffic was displayed preceding this event. After approximately another minute of elapsed flight time; a descending aircraft (along with its tail number) eventually appeared on my ADS-B displays in close proximity to my aircraft. However; neither my tablet display nor my panel avionics annunciated an audible traffic conflict warning.This event reinforces the limitations of both visual see-and-avoid and ADS-B traffic displays when non-collaborating aircraft are maneuvering near each other. As always; pre-flight planning; situational awareness; visual scanning; aviate/navigate/communicate priorities; and constant vigilance are paramount to overcome these limitations.
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.