 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Uav ground crew reported a near midair collision with low flying aircraft that was not flying the airport traffic pattern.
| Attributes | |
| ACN | 1638145 |
| Time | |
| Date | 201904 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | ZZZ.Airport |
| State Reference | US |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | UAV - Unpiloted Aerial Vehicle |
| Operating Under FAR Part | Other 107 |
| Flight Phase | Cruise |
| Route In Use | Other UAS Flight |
| Flight Plan | VFR |
| Aircraft 2 | |
| Make Model Name | Small Aircraft |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Initial Approach |
| Person 1 | |
| Function | Pilot Not Flying |
| Qualification | Flight Crew Commercial Flight Crew Multiengine Flight Crew Instrument Flight Crew Flight Instructor |
| Experience | Flight Crew Last 90 Days 6.2 Flight Crew Total 850 |
| Events | |
| Anomaly | Conflict NMAC Deviation - Procedural FAR Deviation - Procedural Published Material / Policy |
| Miss Distance | Horizontal 100 Vertical 50 |
Narrative:
The uas company has ZZZ's permission to conduct uas operators out of ZZZ airport. Our operations are always south of runway xx/ xy and at or below 400 feet AGL to comply with part XX7 regulations. We were conducting uas training out of ZZZ. We were in the air in cruise flight just south of runway xx; staying clear of the departing and departure ends of all runways. Mid-afternoon; [aircraft Y] made a call mentioning he was coming into landing runway xy. The individual did an extremely low pass down runway xy near the aircrafts max speed. Everything was ok; until the individual decided to make an immediate left turn towards us which departed the runway heading and cut short of the end of the runway. At that point; we tried to direct the uas the best we could to stay clear of the aircraft; but there was little to no time to do so. The individual did a 60 to 90 degree bank maneuver over our operations around 300 AGL to 500 AGL and came extremely close to our uas which weighs around 15 lbs. Where we operate; there should be no manned aircraft in this area as it is not a part of the standard traffic pattern. The individual also knows that there is uas operations in that area and that people are in the area.
Original NASA ASRS Text
Title: UAV ground crew reported a NMAC with low flying aircraft that was not flying the airport traffic pattern.
Narrative: The UAS Company has ZZZ's permission to conduct UAS Operators out of ZZZ Airport. Our operations are always South of Runway XX/ XY and at or below 400 feet AGL to comply with Part XX7 Regulations. We were conducting UAS Training out of ZZZ. We were in the air in cruise flight just south of Runway XX; staying clear of the departing and departure ends of all Runways. Mid-afternoon; [Aircraft Y] made a call mentioning he was coming into landing Runway XY. The individual did an extremely low pass down Runway XY near the aircrafts max speed. Everything was ok; until the individual decided to make an immediate left turn towards us which departed the runway heading and cut short of the end of the runway. At that point; we tried to direct the UAS the best we could to stay clear of the aircraft; but there was little to no time to do so. The individual did a 60 to 90 degree bank maneuver over our operations around 300 AGL to 500 AGL and came extremely close to our UAS which weighs around 15 lbs. Where we operate; there should be no manned aircraft in this area as it is not a part of the standard traffic pattern. The individual also knows that there is UAS operations in that area and that people are in the area.
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.