For this lab, we conducted two 3D mapping missions using the Skydio 2+ on September 16, 2025. The primary objective of these missions was to gain experience using Skydio’s 3D scanning functionality to capture complete scans of vertical and irregular objects.
The missions were conducted at the Purdue University Student Farm. Weather conditions were ideal, with calm winds, clear skies below 12,000 ft, and temperatures well within operational limits. Two scan subjects were selected: a small shed near the parking lot and a nearby light pole.
Prior to each scan, a full briefing was conducted between the Pilot in Command (PIC) and Visual Observer (VO). Crew roles were swapped after completion of the first scan. During initial setup, we encountered issues initializing the Skydio 3D scan workflow. The first aircraft lacked the 3D scan option despite being rebooted into 3D mode, which we believe was caused by a licensing issue. A second aircraft also failed to initialize due to fault codes V110 and V66.
Figure 1. Skydio fault code V110 during initialization
Figure 2. Skydio fault code V66 during initialization
After consulting Purdue UAS dispatch documentation, we identified that the errors were related to Skydio licensing. Once the licenses were refreshed, the aircraft initialized correctly and we were able to proceed with both 3D scan missions.
3D Scan Mission Descriptions
The first mission involved scanning a small shed using the standard Skydio 3D scan mode. A polygon was defined around the structure, allowing the aircraft to autonomously capture imagery while avoiding nearby obstacles such as a chain-link fence.
Figure 3. Small building (shed) selected for standard 3D scan
The second mission used the Skydio tower scan mode to scan a light pole. This mode allowed us to define a cylindrical scan volume around the structure, enabling complete vertical coverage with minimal setup time.
Figure 4. Light pole selected for tower scan mission
Small Building / Shed Scan
Overall, this lab provided hands-on experience with Skydio’s 3D scanning workflows and highlighted how scan type, object geometry, and mission parameters affect scan duration, image count, and dataset size.