Part 107 UAS pilot reported flying in controlled airspace and within an active TFR without authorization.
Synopsis
Part 107 UAS pilot reported flying in controlled airspace and within an active TFR without authorization.
Narrative
During a commercial UAS mission as a wedding videographer capturing video for a high-profile client's wedding day; I was involved in an inadvertent deviation from 14 CFR Part 107 regulations. This resulted in unauthorized entry into Class C airspace and two active Temporary Flight Restrictions (TFRs); an altitude excursion up to 1;407 feet AGL; and operation beyond visual line of sight (VLOS). This event was a direct result of task saturation; accumulated stress and fatigue; and a total breakdown in situational awareness following a last-minute change in mission location.The day prior to the event; the client moved the 'getting ready' location where I was to start filming at a residence in Location X. This new location was within the area of the ZZZ Class C airspace and encompassed by two active TFRs.On the day of the event; I was experiencing significant fatigue from my primary 9-5 job and family obligations - parental responsibilities relating to my children - as well as the stress that comes with filming a wedding day. Upon arrival; I perceived the immediate surroundings and house/filming location as unsuitable for the high-production-value shots required for this celebrity client. Driven by the last minute plan change; pressure to deliver and stress of a 10-12 hour wedding day; I developed 'tunnel vision' and inadvertently bypassed pre-flight planning and a safety checklist.I launched my DJI Mini 4 Pro and given the house was not suitable for filming; focused entirely on trying to get surrounding shots and the camera composition. I inadvertently climbed to 1;407 feet AGL at the highest point to scout for better angles; flying in restricted airspace and beyond VLOS. I was focused on the controller screens image/video shot composition rather than the aircraft's details and position in the airspace. The deviation was identified when a law enforcement officer approached me as I was beginning to bring my drone back for landing. I immediately complied and landed the aircraft safely. No damage whatsoever nor 'close-calls' with manned aircraft or anything occurred.Human Performance & Contributing Factors:Task Saturation & Pressure: The high-stakes nature of the client created significant internal pressure; which resulted in unintentional task-saturation. This caused me to inadvertently focus on cinematography to the exclusion of active airspace monitoring and regulatory compliance.Stress & Fatigue: Accumulated fatigue along with the stress of a wedding day negatively impacted my decision-making and judgment.Loss of Situational Awareness: Due to the last minute change in mission location and pressures of event timeline; I failed to verify the airspace; resulting in a total loss of situational awareness regarding the active TFRs and Class C airspace.Administrative Oversight (Currency Lapse): I identified a lapse in my Part 107 regulatory currency. This was an inadvertent error caused by a misunderstanding of the transition from the previous in-person testing requirements to the current online FAASTeam renewal system and my lack of a formal digital tracking system for my credentials contributing to this oversight.Corrective Actions To prevent a recurrence; I have initiated a comprehensive Safety Improvement Plan:Immediate Compliance: I have confirmed the registration of the UAS involved and affixed the registration number to the aircraft as of Day 0. Having identified the currency lapse mentioned above; I have successfully completed the FAASTeam ALC-677 course to officially restore my regulatory currency and recency of knowledge as of Day 0.Procedural Safeguards: I have created a digital flight log and developed a physical pre-flight safety checklist and inserted it directly on top of my drone in my UAS transport case as a mandatory 'gate' before flight.Technical Safeguards: I have implemented a 'Hard Ceiling' protocol in my flight software for my maximum altitude by setting the UAS maximum altitude limit to a baselineof 65 feet prior to every mission; which is the lowest my UAS software allows me to set it; creating a mandatory technical 'gate.' This requires me to perform a conscious manual override and input the specific airspace ceiling for each new location before the UAS can climb; effectively preventing inadvertent altitude or airspace excursions.Continuing Education: Within days of my incident; I completed the below exams and courses:ALC-677 Part 107 Small UAS Recurrent TestALC-723 10 Decision-Making Concepts for UAS PilotsALC-42 Airspace; Special Use Airspace And TfrsALC-678 sUAS Safety & Risk MitigationALC-803 sUAS Regulations; Laws; Airspace Ownership and FAA EnforcementResource Management: Going forward; I will evaluate mission complexity during the pre-flight phase and utilize a Visual Observer for any operations involving high-density areas or high-pressure environments.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.