Introduction and Objectives
Figure 1. Venky D. and Jacob S. flying M300
Thermal mapping offers an efficient, safe, and cost-effective way to detect things that visible light cameras might miss. For example, living targets, fires, heat losses, etc. Thermal cameras offer early problem detection, safety and risk reduction, and enhanced situational awareness.
My team and I used the DJI M300 equipped with an H20T sensor in this thermal mapping mission. In addition, we used a GNSS and gathered static data that will be used as a base station in the future. My team and I had two main objectives.
Discover, identify, and implement the creation of a mapping mission using the M300 equipped with thermal sensors. Understand the fundamentals of ground control and setting up a static base. Who
Pilot in Command: Dr. Hupy and Jacob Sieber
Thermal Camera/Sensor Operator: Venky Devapatla
Visual Observers: Isabella Avedician, Joe Kahi, Mason Cramer, Hailey Manuel, Nik Auclair
Where
Figure 2. Location of mission
William H. Daniel Turfgrass Research and Diagnostic Center
1340 Cherry Lane West Lafayette, Indiana, 47906
What and Why
Figure 3. M300, landing pad, and sensor set-up
Equipment
The M300 can carry high-resolution payloads like thermal cameras. This allows for detailed and accurate data collection. The M300 can also operate in a dual control mode, allowing one person to focus and control the thermal camera while the other focuses on flying the UAS. The H20T is a quad-sensor solution. It is a multi-sensor payload that has unique intelligence and can capture aerial imagery for a range of drone applications. Site Conditions and METAR
Figure 4. METAR for KLAF and site
Purdue University Airport
Figure 5. Site Conditions
The day of the flight, the sky was clear, minimal wind, and a hot sunny day. All weather was within Part 107 regulations.
LAANC
Figure 6. LAANC authorization for this mission
The mapping mission was conducted in Class D airspace due to proximity to Purdue University Airport, KLAF. My team and I were authorized LAANC in this area. Our maximum height was 200 ft AGL, and we gave all right-of-way to manned aircraft; however, there were no incidents where we needed to adjust the M300’s altitude to avoid a manned aircraft. Hazards
Figure 7. Golfers
Figure 8. People working on turf grass
Figure 9. Parked Cars
Figure 10. Trees
Risk Mitigations
The people playing golf were not near where we were flying the M300. The golf balls were being hit north of where our base set-up was. We also planned to fly at 200 ft AGL, which would avoid any collisions. The people working on the turf grass were made aware of our presence, and we did not fly directly over them. The parked cars were northeast of our base station set-up. We did not fly the drone over any parked cars. The trees were to the north of our base station set-up, and the M300 was not near them. Set-Up
Figure 11. Parameters for flight
Dr. Hupy checked out the M300 and sensor from Purdue University dispatch. Upon arrival at the site, we completed a manual inspection of the M300. We checked to ensure we had enough batteries charged, four total, looked at the propellers, and inspected the body of the M300. We also looked at the H20T sensor. The M300 and H20T were in good condition to operate.
Next, we confirmed the METAR and made sure all weather conditions were acceptable for the M300. We also ensured we had LAANC authorization due to our proximity to the Purdue University Airport, Class D Airspace. Next, we checked the make sure all had their Part 107 license, approved identification, and went over roles, responsibilities, and objectives.
Then came setting up the M300. We, the VOs, first installed the legs and locked them into place. Next, we took the 300 out of the case and set it on a level surface. We took off the caps, installed the batteries, and locked them into place. Next, we attached the H20T sensor and made sure that it was locked and in the correct position. Finally, we put the M300 on the launch pad. While the VOs were setting up the M300, Venky D, Jacob S, and Dr. Hupy were setting up the controller for the M300 and the sensor. Mode 2 was used for the controllers.
Before leaving the Purdue University Airport, we learned how to create a mission in Google Earth and mapped out our flight plan before the flight mission. After the drone, sensor, and controllers were set up, we set out our parameters.
Parallel ‘lawn mower’ grid 90% lateral and frontal overlap We set the overlap to 90% due to the bit depth not being enough Bit depth is the number of bits used to store each unit of data in a digital file Lack means the image file has less resolution, resulting in a lower number of available colors or amplitude levels Return-to-Home (RTH) = 25% battery life We did not have to use RTH and only used one set of batteries Maximum Altitude = 200ft AGL Maximum altitude also allowed for LAANC authorization Issues Encountered
When setting up the M300, the crew and I faced a preflight check issue. It warned us to make sure the drone's arms were unfolded and fixed in place. In addition, the RTX was enabled, and when we were trying to troubleshoot the issue, the DJI pilot app was displaying that we were exceeding our maximum flight altitude, calculating, and inputting incorrect flight data. We fixed this issue by changing the flight settings to IR.
Once the setup was complete, all parameters were set, issues were resolved, and all participants were aware of roles and responsibilities, it was time to conduct the flight mission.
Data Gathered and Deliverables
Time to drive to field and set-up
7 minutes from Purdue Airport to Site location Set-up was about 45 minutes due to issues encountered
METADATA
Location: William H. Daniel Turfgrass Research and Diagnostic Center
Date: 09/30/2025
Vehicle: M300
Sensor: H20T
Battery: 2 lithium batteries needed, 2 back-up
Approval # (LAANC/COA/Waiver) - Yes
Flight Information
-------------------
Flight Number: 1
Takeoff Time: 1500
Landing Time: 1518
Altitude (m): 200 ft AGL
Sensor Angle: Nadir (-90 degrees)
Overlap: 90%
Sidelap: 90%
Ground Control
------------------
System used (ie PPK, RTK, Aeropoints) - GNSS
Coordinate System: GPS
Weather
------------------
Cloud Cover: Clear Sky
Wind Direction: 50 degrees true north (NE)
Wind Speed: 9 knots
Temp: 29.44 C
Crew
------------------
PIC: Jacob Sieber
VO: Isabella Avedician, Joe Kahi, Mason Cramer, Hailey Manuel, Nik Auclair, Dr. Hupy
Submitter: All
Summary
My team and I went into this flight mission wanting to discover, identify, and implement the creation of a mapping mission using the M300 equipped with a thermal sensor, and to understand the fundamentals of ground control and setting up a static base. These objectives were successfully met due to pre-flight planning, collaboration, and execution.
Several key stages went into the mapping mission.
Determining mission objectives Planning flight route and parameters Overlap, altitude, gimbal angle, and sensor resolution Weather conditions and LAANC Setting up the M300 and thermal sensor Later processing the data
In addition, my team and I compared the timing and differences of the M300 mapping mission to prior missions flown with different types of UAS. We spent more time in the pre-flight phase due to the M300 being a more advanced and bigger UAS, and due to the issues encountered with our flight route. We were also able to operate in Dual Mode, which allowed one operator to focus specifically on the thermal sensor and gimbal, and the other operator to focus on the UAS flight path and battery life. This allowed us to be more efficient in collecting our data while keeping safety a priority.
Finally, we used a GNSS ground control station to collect real-time data. The GNSS ground station was in a fixed, known location tracking GNSS satellites. The ground station can monitor signals, collect atmospheric data, and determine precise satellite position, while giving us highly accurate data. The GNSS ground station was also providing terrestrial reference points that we will later process in future labs.
OneDrive Link: