37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1531194 |
Time | |
Date | 201803 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Light | Daylight |
Aircraft 1 | |
Make Model Name | PA-32 Cherokee Six/Lance/Saratoga/6X |
Operating Under FAR Part | Part 91 |
Flight Phase | Initial Climb |
Aircraft 2 | |
Make Model Name | UAV - Unpiloted Aerial Vehicle |
Operating Under FAR Part | Other 107 |
Flight Phase | Cruise |
Person 1 | |
Function | Single Pilot Pilot Flying |
Qualification | Flight Crew Instrument Flight Crew Private |
Experience | Flight Crew Last 90 Days 15 Flight Crew Total 800 Flight Crew Type 200 |
Events | |
Anomaly | Conflict NMAC Deviation - Procedural FAR |
Miss Distance | Horizontal 30 Vertical 0 |
Narrative:
ZZZ was operating under a notamed closed runway with permission to depart giving by the airport coordinator 5 minutes before taxi. A film crew with a helicopter and a small drone was operating at the airport. Upon announcing on the CTAF that the aircraft was under back-taxi on the runway to the run-up area to avoid the helicopter near the taxiway; an unknown (possibly helicopter operator) asked a 20-25 minute delay in taxi. Due to an arrival schedule and perceived unreasonable request by the unknown requester it was communicated that the taxi delay request could not be accommodated by the aircraft. The aircraft entered the runway and was in the process of taxi when the helicopter air-taxied onto the runway without further communication. The aircraft transmitted on the CTAF that the runway was occupied. The helicopter replied that the runway was closed for their use. The aircraft stopped taxi operations on the runway and held position. The helicopter then continued to fly low passes over the aircraft (approximately 15 ft above the aircraft) and along the entire runway length with aggressive maneuvering. During one of the helicopter passes; when the helicopter was clear of the aircraft; the aircraft completed the back-taxi to the run up area and waited for the helicopter to clear the runway. When the helicopter landed again; the aircraft requested status from the helicopter on the CTAF. The query was not replied to. The aircraft made a takeoff call and entered the runway. A normal takeoff was accomplished; however during the climb out at an altitude of approximately 75 ft; an unexpected and unknown drone quadcopter was observed hovering adjacent to the runway between the taxiway and runway. This drone was passed with approximately 30 ft of horizontal distance and 0 ft of vertical clearance. No communication from the drone was observed. The pilot of the aircraft felt that the helicopter performed a dangerous and unnecessary maneuver near the aircraft that had the right of way. The pilot also feels that the drone operator took an unnecessary risk by operating the drone in the vicinity of a departing aircraft without prior arrangement or communication with the aircraft. Both of the situations could have been avoided with better coordination from the airport coordinator and with increased communication from the helicopter and drone pilots.
Original NASA ASRS Text
Title: PA32 pilot reported a drone flew approximately 30 feet away in the departure corridor during the initial climb out.
Narrative: ZZZ was operating under a NOTAMed closed runway with permission to depart giving by the airport coordinator 5 minutes before taxi. A film crew with a helicopter and a small drone was operating at the airport. Upon announcing on the CTAF that the aircraft was under back-taxi on the runway to the run-up area to avoid the helicopter near the taxiway; an unknown (possibly helicopter operator) asked a 20-25 minute delay in taxi. Due to an arrival schedule and perceived unreasonable request by the unknown requester it was communicated that the taxi delay request could not be accommodated by the aircraft. The aircraft entered the runway and was in the process of taxi when the helicopter air-taxied onto the runway without further communication. The aircraft transmitted on the CTAF that the runway was occupied. The helicopter replied that the runway was closed for their use. The aircraft stopped taxi operations on the runway and held position. The helicopter then continued to fly low passes over the aircraft (approximately 15 ft above the aircraft) and along the entire runway length with aggressive maneuvering. During one of the helicopter passes; when the helicopter was clear of the aircraft; the aircraft completed the back-taxi to the run up area and waited for the helicopter to clear the runway. When the helicopter landed again; the aircraft requested status from the helicopter on the CTAF. The query was not replied to. The aircraft made a takeoff call and entered the runway. A normal takeoff was accomplished; however during the climb out at an altitude of approximately 75 ft; an unexpected and unknown drone quadcopter was observed hovering adjacent to the runway between the taxiway and runway. This drone was passed with approximately 30 ft of horizontal distance and 0 ft of vertical clearance. No communication from the drone was observed. The pilot of the aircraft felt that the helicopter performed a dangerous and unnecessary maneuver near the aircraft that had the right of way. The pilot also feels that the drone operator took an unnecessary risk by operating the drone in the vicinity of a departing aircraft without prior arrangement or communication with the aircraft. Both of the situations could have been avoided with better coordination from the airport coordinator and with increased communication from the helicopter and drone pilots.
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.