Problem viewing CLICK HERE
Subscribe
NASA Aviation Safety Reporting System (ASRS) - UAS Safety in Sight
June 2023
drones around airport
Sharing the Skies
The sky is vast with plenty of airspace to share. However, with shared airspace comes shared responsibility for ensuring safety of flight. When operating in the airspace both drone pilots and crewed aircraft pilots must maintain vigilance and an awareness of other traffic for the sake of safety. 

Drone pilots are responsible for knowing the position of their drone in relation to other aircraft, maintaining a safe distance, and giving the right-of-way to other aircraft. Drone pilots are also required to get authorization, typically through an approved Low Altitude Authorization and Notification Capability (LAANC) app or from the FAA Drone Zone, to fly under 400 feet in controlled airspace including at and around airports. It is important to remember that even when flying with proper authorization, there might still be low-flying aircraft in the area that are unaware of drone operations.

Crewed aircraft pilots use see-and-avoid techniques to spot other craft. However, it can be very easy to miss something as small as a drone or model aircraft, especially in low-visibility conditions. Crewed aircraft pilots may also not be able to maneuver quickly enough to avoid potential airborne conflicts.

This issue of UAS Safety In Sight presents excerpts from reports about drone operations at and around airports from multiple points of view.
Low Level - High Alert
Helicopter Pilot Reported the Following:
ACN: 1871974
I...had a mid-air collision with an unknown object…flying…around 300 ft. I collided with something which at first I thought was a bird but upon later inspection on the ground, I believe it to be a drone. I was unable to see the object since it came from below and was out of my field of view.... A big factor in this collision was flying low level close to the shore over the water. Drones and helicopters have rights to be in the same airspace under certain conditions and where I was it was legal for them to be there but for me as well. A corrective action for me would be to be mindful that drones could be up to 400 ft. legally and to not fly as low over the shoreline any more.   
Through the Haze
General Aviation Pilot Reported the Following:
ACN: 1828483
Aircraft was on final approach segment.... Conditions were hazy with scattered clouds... [I] noted rapidly approaching target and banked left. Both [pilots] noted a large UAV (drone) pass within 1/4 mile of right wing…[I] was able to recover to stabilized approach and land without further incident.... Operating a drone on final approach course to airport, [in these weather conditions] is extremely careless and reckless. Due to haze conditions, the unlighted drone was difficult to spot...
Meticulous Planning Modified
Commercial UAS Pilot Reported the Following:
ACN: 1884993
Crew consisted of 4 people and 2 UAS.... One of the pilots and support person were monitoring the ATC radio communications. The operation consisted of manual, synchronized flight of both UAS… The UAS Pilots were in constant communication with each other…and followed all special provisions outlined in the COA [Certificate of Authorization] including contacting the Tower prior to starting… and monitoring the tower frequency … during UAS flights... Once the ascent rate was achieved… [UAS-1 Pilot] looked up … and immediately noticed a low flying manned aircraft dangerously close, with a heading directly in line with UAS-1…We estimate that manned aircraft was 60 ft directly below UAS-1 at time of the near miss… After the incident, … the team discussed better ways of avoiding incoming manned aircraft… [and] decided that in all high air-traffic scenarios the team must have at least one member whose only responsibilities are monitoring air-traffic radio frequencies and visually checking for intruding aircraft…
Note the NOTAM
UAS Visual Observer Reported the Following:
ACN: 1823676
...[A large UAS and a helicopter] had a near miss incident… [while] conducting flight tests in the local area and training in the [airport] traffic pattern....[I, the Visual Observer] noticed the helicopter was headed [toward the] airport... about 200-300 feet Above Ground Level (AGL). [I] notified the UAS that there was traffic converging in their flight path. …[The UAS] ended up leveling to pass under the helicopter…[and] came within about 20-50 feet …We believe the helicopter [pilot] failed to read the NOTAMS around the local area saying there is UAV activity in the area…and clearly did not see the UAS as he did nothing to attempt to climb, descend, or turn.  
Drone Unseen, but Avoided
Flight Instructor Reported the Following:
ACN: 1850939
I was doing a flight with my private student and was in the traffic pattern for [the] Runway, on the third lap in the pattern I saw something in my peripheral vision. My student couldn't see it due to the altitude the engine cowling was blocking his vision, there was a drone that was at approximately 1,100 ft. I quickly pulled the yoke back to gain altitude to avoid the drone that was right in front of us. I reported it to the Tower ... the Controllers did not see it.
ASRS Database Online
To view these reports and other UAS reports, visit the ASRS Database Online: 
Visit Database Online
Would you like to learn more about the NASA Aviation Safety Reporting System?
View this pre-recorded webinar on UAS reporting to ASRS here: 
View ASRS Webinar
USIS-006
Aviation Safety Reporting System
LinkedIn Share