Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Update the title following the format: Jan 01, 2023 - RCA Name

📋Incident overview

Postmortem owner

Airframe

Related incidents

Incident date

Approx. Damage Costs

Report Date

🔮 Executive summary

  • During this debrief we are reviewing the crash footage & Ardupilot telemetry logs

    • "batteries sag to <3v per cell during transition"

    • Had trouble maintaining fixed wing attitude

      • Looking at logs is that the elevator input makes almost no change in attitude

        • Could’ve been caused by airspeed being too low

    • Roll input is weak as well

      • Possibly all of our control surfaces are weak due to low airspeed ?

        • As we get faster servos require more power to work

        • Consider making controls out of something else, maybe a different

    • From logs it started falling as soon as the quad motors shutoff

      • Prime theory is we weren't going fast enough when quad motors shutoff

      • yaw is a bit weird but possibly not the issue

      • We should check pixhawk parameters and that would give us more information

⏱ Incident timeline

Describe (approximate) timelines, cross-correlate with telemetry/video recordings/etc if any.

⛑ Postmortem report

Instructions

Report

(warning) Leadup

List the sequence of events that led to the incident.

🙅‍♀️ Fault

Describe what didn't work as expected. If available, include relevant data visualizations.

👁 Detection

Report when the team detected the incident and how they knew it was happening. Describe how the team could've improved time to detection.

🙋‍♂️ Response

Report who responded to the incident and describe what they did at what times. Include any delays or obstacles to responding.

🙆‍♀️ Recovery

Report how the user impact was mitigated and when the incident was deemed resolved. Describe how the team could've improved time to mitigation.

🔎Five whys root cause identification

Run a 5-whys analysis to understand the true causes of the incident.

🗃Related records

Check if any past incidents could've had the same root cause. Note what mitigation was attempted in those incidents and ask why this incident occurred again.

🤔 Lessons learned

Describe what you learned, what went well, and how you can improve.

✅ Recommendations for future

Actionable Recommendation

Reasoning

  • No labels