2025-07 · NASA ASRS report 2262591
Part 107 UAS pilot reported inadvertently flying into a TFR without authorization. Upon recognizing the airspace incursion; the pilot immediately ended the flight.
While acting as the Remote Pilot In Command (RPIC) of my UAS with a controller; I inadvertently entered restricted airspace covered under an active Stadium TFR surrounding Target Field in Minneapolis. At the time of the flight; the skies were clear with calm winds. The flight took place just before sunset; and the take-off location was North East of the stadium (inside the 3NM restriction area) and 5.5NM North of MSP. The drone launched from a public area in a residential neighborhood. The flight took place at altitudes between ground level and 394ft AGL; and a max distance of 364ft away from the take off point and maintained VLOS. I was the only person involved in this operation. I used the mobile app 'Air Control' (iOS version: v2.10.0.2025050200 by Aloft) to check airspace as part of my pre-flight checklist. The airspace in the area of operation is Class G; underneath the MSP Class B shroud; but outside of the LAANC authorization radius from MSP. There were multiple airspace 'notifications' displayed in the app for multiple stadiums; the National Park Service (NPS) Mississippi River Valley; and uncontrolled hospital heliports; making for complex airspace. I was aware of the rules for stadium TFR's; but made the mistake of not realizing there was an active event at that stadium and that I was inside of the 3NM radius. When I noticed the stadium lights were illuminated; it caused me to question my proximity to the stadium and the possibility of an active game; and I terminated the flight. Aside from the TFR incursion; the flight was uneventful; and there were no other safety issues. After landing I determined that there was an event taking place. While I take full responsibility for the flight and my lapse in situational awareness; I think contributing factors include:- Extra steps required to check scheduled times for covered events at stadiums; since there is no service that I am aware of that lists precise times that a Stadium TFR is in effect.- A slightly confusing interface in the Air Control iOS app that shows a map with yellow circles around airspace 'notification' areas; but no way to determine which circle belongs to which notification.- A slightly confusing interface in the iOS Air Control app that only shows 3 'notifications' in a list at a time; without a visual scrollbar; requiring that you notice an indicator number and then manually scroll through the list. The scrollbar appears only when you are actively scrolling the list.- My lack of experience flying in this specific area (less than 10 operations in this area).- My own haste in executing the flight before sunset.To improve my ability to execute safe and legal flights in the future I plan to investigate better methods for determining if there is an active Stadium TFR; take more time to pre-plan my flight when operating in areas with airspace notifications and restrictions; and recommit to the IMSAFE checklist to ensure I'm not rushing a flight. I also believe a system to inform all pilots of active Stadium TFR's would increase situational awareness and airspace safety.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.
Loading the flight search…
Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.
We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.
Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.
Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.