Skip to content

DJI Flight Log Analysis

10 points
Nathan Tyler Rose
Last edited 14 days ago by Lucas Isaiah Toppe.

Overview

You will conduct a detailed analysis of a real-world UAS crash event to demonstrate your ability to apply analytical techniques, interpret evidence, and recommend improvements based on flight data, recovered aircraft, safety reports, and lessons learned.
You will analyze the crash of a Purdue UAS fleet aircraft, DJI M300 C. The data resources are linked below.

Data Resources

Safety Report

Crash Analysis Lecture (for photos)

Flight Records

This log is decrypted below using

Report Instructions

Teams

You may work in small groups (2-3). Be sure that you fully understand your team’s submission (you may have related questions on your
Broken link
.

Formatting Tips

Page requirement: None – your report should be concise, but comprehensive. Missing content will count against your score as much as irrelevant or poorly written content.
Figures, tables, and diagrams are highly encouraged (you’d have a difficult time making the case without them.

Contents

1. Background and Context (15%)
a. Summarize the basic facts: date, location, parties involved, and nature of the crash.
b. Describe the system, vehicle, or software involved.
2. Root Cause Analysis (30%)
a. Investigate and identify the primary and contributing causes.
b. Discuss mechanical failures, human errors, design flaws, environmental factors, or regulatory (FAA, Purdue, Dispatch, etc.) oversights.
c. You may wish to use a simplified to demonstrate the failure inputs
3. Crash Dynamics (25%)
a. Explain the sequence of events during the crash, including forces, motions, and any failure mechanisms.
b. Support your analysis with calculations, graphs, diagrams, or a crash reconstruction in 3D space.
4. Post-Crash Response and Consequences (10%)
a. Summarize the response and immediate aftermath.
b. Identify the required reporting requirements.
c. Discuss impacts, actions, and potential policy changes resulting from the event.
5. Recommendations (15%)
a. Propose design, operational, or regulatory (FAA, Purdue, Dispatch, etc.) changes that could have prevented the crash.
b. Support your recommendations with evidence and logical reasoning.
6. Report Structure and Quality (5%)
a. Your report must be clear, concise, professional, and well-organized.
b. Include references in a recognized citation style (APA, IEEE, etc.).

Deliverables

Upload a well-formatted written report to Brightspace in PDF format by the due date.
Want to print your doc?
This is not the way.
Try clicking the ··· in the right corner or using a keyboard shortcut (
CtrlP
) instead.