Part 107 UAS pilot reported their crew flew in a TFR area without authorization. All remaining flights were grounded for the duration of the TFR.
Synopsis
Part 107 UAS pilot reported their crew flew in a TFR area without authorization. All remaining flights were grounded for the duration of the TFR.
Narrative
I (RPIC) instructed Person A to execute mission to conduct a functional flight test; at XA:11AM; on Day 0. During the test the drone hovered at 50 ft. AGL for less than 15mins; during the time there was a TFR that was inplace for Location X approx. 2.6 miles away from take off location. Once we landed we received a call from Person B that there was currently a TFR; after receiving the information we checked both the FAAs TFR website and air control (app) to verify the TFR and did not see any TFRs in the location; it was only till we used foreflight that we found the TFR; something not apart of our checklist. After learning about TFR our mission remained ground[ed] for rest of day due to the length of the TFR.I believe the reason for the airspace incursion was due to need to get up and running in a quick time; and not checking TFRs and NOTAMs before the test per company rules; along with websites like 1800wxbrief.Changes to prevent airspace violations will be checking 1800wxbrief; before you fly; and foreflight; and checking for NOTAMs before flight.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.