37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1636949 |
Time | |
Date | 201904 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | PXR.VORTAC |
State Reference | AZ |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | UAV - Unpiloted Aerial Vehicle |
Operating Under FAR Part | Other 107 |
Flight Phase | Takeoff |
Flight Plan | None |
Person 1 | |
Function | Check Pilot |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Total 16000 |
Events | |
Anomaly | Airspace Violation All Types Deviation - Procedural FAR Deviation - Procedural Published Material / Policy |
Narrative:
The purpose of this report is to report a laanc portal that is not operating properly which contributed to a possible airspace incursion by our uas.at location number 1 (030- degrees at 2.0 NM from pxr VOR); the PIC requested a laanc airspace waiver through the airmap program. On the 'flight briefing' screen there was an amber banner that stated 'authorization upon submission' notice. The PIC then pressed the blue 'submit flight' button and a screen balloon appeared stating 'success - your flight plan has been submitted'. The airmap program then displayed a map screen and a flight time banner appeared with a clock running just above a bottom blue banner labeled 'end flight'. We then flew twice at this location for a total of 23 minutes.we repeated this process at a location number 2: tempe town lake marina located at 078 degrees at 1.9 NM from the pxr VOR. We flew at location number 2 twice; totaling 15 minutes.while the PIC was operating the drone; I was auditing the flight by looking at airmap on my phone and did not see the flight displayed.I alerted the PIC and he immediately terminated the flight. We tried several times to submit new flights on the PIC's phone; and on my phone; with the same results: airmap processed the waiver requests; displayed normal indications that the waiver would be issued; and then started the flight timer. However; when selecting the flight plan details for previous flights; a red waiver not approved banner became visible even though normal screens appeared when waivers were approved and the flight timer was running.at this point; I contacted a person that is involved in the local aeroscope security network and he advised me to use a different laanc provider.we relocated to location number 3: 076 degrees at 1.5 NM from pxr VOR and used the skyward portal. We immediately received authorization and a waiver number at this location; even though it was a [few] miles closer to phx.we suspect that all four flights at locations number 1 and number 2 may have been flown without FAA approval.therefore; our uas operations manual will be amended to require the FAA waiver authorization number be recorded on our flight manifest prior to takeoff.additionally; we have contacted airmap to repair their iphone app.
Original NASA ASRS Text
Title: DJI UAV operator reported a possible airspace incursion occurred in the vicinity of PXR.
Narrative: The purpose of this report is to report a LAANC portal that is not operating properly which contributed to a possible airspace incursion by our UAS.At location Number 1 (030- degrees at 2.0 NM from PXR VOR); the PIC requested a LAANC airspace waiver through the AIRMAP program. On the 'Flight Briefing' screen there was an amber banner that stated 'Authorization upon Submission' notice. The PIC then pressed the blue 'SUBMIT FLIGHT' button and a screen balloon appeared stating 'Success - Your flight plan has been submitted'. The AIRMAP program then displayed a map screen and a Flight Time banner appeared with a clock running just above a bottom blue banner labeled 'END FLIGHT'. We then flew twice at this location for a total of 23 minutes.We repeated this process at a location Number 2: Tempe Town Lake Marina located at 078 degrees at 1.9 NM from the PXR VOR. We flew at location Number 2 twice; totaling 15 minutes.While the PIC was operating the drone; I was auditing the flight by looking at AIRMAP on my phone and did not see the flight displayed.I alerted the PIC and he immediately terminated the flight. We tried several times to submit new flights on the PIC's phone; and on my phone; with the same results: AIRMAP processed the waiver requests; displayed normal indications that the waiver would be issued; and then started the flight timer. However; when selecting the flight plan details for previous flights; a red Waiver Not Approved banner became visible even though normal screens appeared when waivers were approved and the flight timer was running.At this point; I contacted a person that is involved in the local Aeroscope security network and he advised me to use a different LAANC provider.We relocated to location Number 3: 076 degrees at 1.5 NM from PXR VOR and used the Skyward portal. We immediately received authorization and a waiver number at this location; even though it was a [few] miles closer to PHX.We suspect that all four flights at locations Number 1 and Number 2 may have been flown without FAA Approval.Therefore; our UAS Operations Manual will be amended to require the FAA Waiver Authorization number be recorded on our flight manifest prior to takeoff.Additionally; we have contacted AIRMAP to repair their iPhone app.
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.