Skip to content
Drone Authority
Drone news desk
FinalCommercialIndustry2 min read

DOE drone team mapped 6,000 acres after Typhoon Sinlaku in the Northern Mariana Islands

The agency reports 41 flights, about 38,000 images, field processing, and map delivery into federal recovery systems. It did not publish an independent measure of time or cost saved.

By

DOE field operator hand-launching a fixed-wing mapping drone among storm-damaged trees on Saipan
DOE field operator hand-launching a fixed-wing mapping drone among storm-damaged trees on Saipan. Image: U.S. Department of Energy

Decision brief

The useful part is the full data chain: portable power, launch sites, image capture, field processing, secure upload, map review, and delivery into FEMA's system. DOE gives the scale of the work, but does not compare the results with another response.

Flights
41

From 18 launch and recovery points

Images
About 38,000

Processed into orthomosaic maps

Area mapped
6,000 acres

DOE's reported Saipan total

Field operation

The team collected a large image set from distributed launch sites.

On August 28, the U.S. Department of Energy published a report on its drone work after Typhoon Sinlaku hit the Commonwealth of the Northern Mariana Islands. The team used DOE's Drone Unmanned Camera Kit, or DUCK. It made damage maps for local crews, utilities, and federal agencies. Oak Ridge National Laboratory supplied the kits, software, and support.

DOE says the team completed 41 flights from 18 launch and recovery points on Saipan in late April. It collected about 38,000 images, flew for more than 40 hours, and mapped 6,000 acres. The raw photos became orthomosaic maps. These are stitched aerial images corrected so locations and distances line up.

Data chain

Processing and delivery happened close to the incident, not weeks later in an office.

The field crew used a vehicle inverter to charge batteries and did most of the data work on site. It sent the maps to MAPSTER, Oak Ridge's system for sharing files where internet service is weak. DOE says MAPSTER can help find damaged electrical equipment and support search work. The team also placed the maps in FEMA's ArcGIS system for internal use.

DOE planned to leave after the Sinlaku response. FEMA extended the deployment by 33 days as Typhoon Bavi approached. The agency says the team then worked across Guam, Rota, Tinian, and Saipan, with the heaviest energy damage on Rota. DOE does not give a second set of flight or acreage totals for that phase.

Operational record

The five-part disaster-mapping chain

The aircraft was one part of a field system built to turn imagery into maps that other agencies could use.

  1. 01

    Plan dispersed launch sites

    Use accessible locations that cover the damaged area without assuming roads, power, or communications are reliable.

  2. 02

    Capture a consistent image set

    Maintain overlap, location data, and camera settings that support repeatable map processing.

  3. 03

    Process in the field

    Carry enough power, storage, and compute capacity to build usable products near the incident.

  4. 04

    Move data through a secure system

    Upload the orthomosaics to a platform that supports low-bandwidth work and controlled access.

  5. 05

    Deliver where responders work

    Place the maps in the client's existing GIS rather than asking every user to adopt a separate viewing tool.

Evidence limit

The acreage is documented. The recovery effect is not yet measured.

The report shows that a small field team can gather and deliver many images in hard conditions. It does not say how many repair decisions used the maps. It also does not state the hours saved, mission cost, or accuracy of the software's damage flags compared with a person's review. Those gaps matter if another team cites this job as proof of performance.

For a mapping business, the client needs the map, not a high flight count. A response kit needs power, storage, offline processing, a consistent coordinate system, image quality checks, controlled sharing, and a destination the client already uses. The DOE team connected those steps. Its public report does not measure the final effect on recovery.

Build a professional mapping workflowSee how capture, control, processing, quality checks, and delivery fit together for paid mapping work.

Practical read

What the case study supports

Strong fit

  • Emergency managers designing a drone mapping and data-delivery workflow
  • Utilities planning damage assessment when roads and grid power may be unavailable
  • Commercial mapping teams defining the field equipment behind a reliable deliverable

Account for

  • Treating an agency-reported acreage total as an independent outcome study
  • Buying aircraft without planning field power, processing, storage, and GIS delivery
  • Using machine-learning output without documenting human review and error handling

Source file

Verify the reporting

Continue on Drone Authority

Put the report to work

Continue this beat

More commercial reporting

Follow commercial

Editorial standard. Claims are tied to the sources on this page. Material corrections are logged publicly and can be sent to corrections@droneauthority.org.

How the news desk works