← Latest papers
💻 computer science

UAV-SEAD: State Estimation Anomaly Dataset for UAVs

This paper introduces UAV-SEAD, a large-scale, real-world dataset comprising over 52 hours of flight logs from PX4-based UAVs that categorizes state estimation anomalies into four distinct classes to advance the development and evaluation of realistic anomaly detection systems.

Original authors: Aykut Kabaoglu, Sanem Sariel

Published 2026-02-17
📖 4 min read☕ Coffee break read

Original authors: Aykut Kabaoglu, Sanem Sariel

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). ✨ This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine you are teaching a child to ride a bicycle. You want them to stay balanced, know where they are going, and not crash into a tree. Now, imagine that child is a drone (a UAV), and instead of a human brain, it has a computer trying to figure out: "Am I tilted? Am I moving fast? Where am I exactly?"

This computer is called a State Estimator. It's like the drone's internal GPS and gyroscope combined. It constantly guesses where the drone is based on what its sensors (cameras, barometers, accelerometers) tell it.

The problem? Sometimes, the sensors get confused, the battery acts up, or the wind blows too hard. The drone's computer might think it's hovering in place when it's actually drifting toward a wall. This is called a State Estimation Anomaly. If the drone doesn't realize it's confused, it might crash.

The Problem: "Fake" Data vs. Real Life

Until now, researchers trying to teach computers how to spot these mistakes mostly used simulations. It's like teaching a pilot to fly by only playing a video game. You can program the game to make the plane crash, but it doesn't feel like the real wind or the real vibration of a broken motor.

Some researchers tried to break real drones on purpose (like cutting a propeller) to see what happens. But that's dangerous, expensive, and you can't do it very often. Plus, you might miss the weird, subtle glitches that happen naturally in the real world.

The Solution: UAV-SEAD (The "Real World" Library)

The authors of this paper, Aykut Kabaoglu and Sanem Sariel, decided to build a massive library of real drone flights. They didn't break anything on purpose. They just flew their drones hundreds of times in warehouses, sports halls, and outside, letting nature and hardware quirks cause whatever problems happened naturally.

They collected 1,396 flights (over 52 hours of footage). This is like recording 52 hours of a child riding a bike, capturing every wobble, every near-miss, and every time they got dizzy, without ever pushing them over.

How They Organized the Chaos

Since they couldn't just say "something went wrong," they created a "dictionary" to describe exactly how the drone got confused. They sorted the mistakes into four main categories:

  1. Mechanical & Electrical (The "Body" Problems):

    • Analogy: Imagine the drone's legs are shaking because a screw is loose, or its heart (battery) is skipping a beat.
    • What happens: The drone vibrates too much, or the power flickers, causing the computer to get dizzy and lose track of its position.
  2. External Position (The "Eyes" Problems):

    • Analogy: The drone is looking at a mirror or a dark room. Its "eyes" (cameras) can't see the ground clearly.
    • What happens: The drone thinks it's moving forward, but it's actually standing still, or it suddenly "teleports" back to where it started because its vision system got confused.
  3. Global Position (The "Map" Problems):

    • Analogy: The drone is trying to use a GPS signal, but it's in a city with tall buildings (like a canyon). The signal bounces off the walls.
    • What happens: The drone thinks it's in a different city entirely. It might suddenly jump to a new location on its map.
  4. Altitude (The "Height" Problems):

    • Analogy: The drone is trying to measure how high it is, but the air pressure changes suddenly, or it flies over a shiny pool of water that tricks its distance sensor.
    • What happens: The drone thinks it's 10 feet off the ground when it's actually 2 feet, or vice versa. It might crash into the ceiling or the floor.

Why This Matters

Think of this dataset as a training manual for a safety guard.

Before this paper, safety guards (algorithms) had to guess what a crash looked like based on video games or broken props. Now, they have a library of 52 hours of real-life confusion. They can study exactly how a drone behaves when it's about to fail.

By studying these "real" mistakes, engineers can build smarter AI that can say: "Hey, I see the battery is dipping and the camera is blurry. I'm not sure where I am, but I'm going to land safely before I crash!"

The Bottom Line

This paper is a gift to the drone community. It says, "Stop guessing with video games. Here is a huge bucket of real-world data where drones actually got confused. Use this to teach your computers how to be safer, smarter, and more reliable."

It's the difference between learning to swim in a bathtub versus learning in a real ocean with actual waves. This dataset is the ocean.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →