Date: 201912
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: UAV - Unpiloted Aerial Vehicle
Operator: Personal
Operating under: Other Part 107
Flight plan: VFR
Mission: Personal
Flight phase: Takeoff / Launch
Airspace: Class B ZZZ
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Commercial
Human factors: Distraction; Fatigue; Training / Qualification; Communication Breakdown
Anomaly: Airspace Violation All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Other Post Flight
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Unintentionally flew drone in ZZZ Class B airspace without authorization for 12 minutes.How the problem arose:1. I assumed authorization of an LAANC request without verifying a text authorization was received.2. A one minute miscalculation caused the LAANC rejection of flying at night. Sunset was at XA:23. Thirty minutes past sunset was XA:53. The request was submitted at XA:09 for a 45 minute flight which puts the request end time at XA:54; one minute past the 30 minute window following sunset.How it was discovered:After the flight I realized I had failed to check for a text message with authorization before takeoff. I found no text message on my phone. I even tried and failed to find a place to view my LAANC request history online to ensure the request had been authorized. In the AirMap app used to make the request; I found the rejected LAANC request in the Flights menu area. Not an area I normally review prior to a flight because it always appeared empty. I thought maybe a bug in the AirMap app or I just didn't understand the purpose of the section. Now I know; after some experimentation; it takes my app a great many seconds to populate Flights. While it loads data the AirMap app displays the message 'no current flights.' I assumed this meant it only displayed currently active flights. Wrong assumption. If you wait long enough it loads all your past requests. And that is how I found the rejection with the reason of flying at night right at the top of the list.Contributing Factors:Fatigue and rushing. Sunset nearing; losing the light. Soon people would be nearby and I did not want to risk flying over them. The scenario made me anxious and nervous and caused me to rush.It had been 3 months since my last LAANC request so I was out of practice using the app.My Conclusions:1. I should have recognized I was rushing and fatigued and slowed myself down or stopped altogether.2. I should have waited until I positively laid eyeballs on a text authorization and known exactly where to find the request status in the app if the text message is not received. Now I do; it's in the Flights menu.3. Had I discovered the rejection I could have easily re-entered with a reduced amount of time. The request would probably have been approved without issue. Of course there could still be other conditions that would cause a flight to be rejected.4. Reviewing AirMap operation; I believe I simply missed or misread the AirMap messages warning that my submission would be rejected. I believe now that I incorrectly pressed continue rather than cancel when asked if I want to continue the flight. This is why the flight timer started and I assumed an approved flight. Poor assumption.Remediations:Training. I have reviewed the AirMap app and believe I understand where my errors occurred and why. I will also look for a detailed training for the AirMap app to see if there are other information and safety features I am unaware of to prevent any future incidents. Authorize flight in advance when possible rather than at the scene immediately before the mission. This allows the request in a neutral environment and time for reflection and adjustment. I did not know until now how to authorize a flight in advance in AirMap. Moving forward I will use that feature.Self-evaluate for fatigue; nervousness or anxiety; etc before flight. Adjust pre-flight procedures. 1. Do not rush. 2. Self evaluate mental state (How are you feeling - BE HONEST). 3. Double check all LAANC request input parameters. READ all AirMap app prompts thoroughly.4. Submit LAANC request. 5. Verify LAANC authorization received in text message and in AirMap Flights menu section. 6. Unpack drone equipment. 7. Perform pre-flight equipment checks.




Synopsis: UAV pilot reported flying and not realizing authorization had been denied.