How to read an anomaly report

Anomaly statements are written by people balancing transparency against an ongoing investigation. The wording is deliberate and it carries information.

The vocabulary

“Off-nominal” means something departed from the expected profile. It says nothing about severity.

“Anomaly” is more serious and usually implies something requiring investigation before the next flight.

“Mishap” is a regulatory term in the US context and triggers a formal, overseen investigation. When that word appears, the schedule impact is real and typically measured in months.

“Range safety action” means the vehicle was destroyed deliberately.

What return-to-flight language tells you

“We expect to return to flight shortly” alongside “the cause has been identified” is a good sign — a known, bounded fault.

“The investigation is ongoing” with no identified cause, several weeks in, generally means the fault is not reproducing or is not understood. Those take much longer.

The corrective-action tell

The most informative part of any final report is the corrective action. A hardware change is bounded and fast. A process change suggests the fault was organisational. A design change is the most serious, because it invalidates prior qualification and can require re-testing that takes quarters.

Reading schedules afterwards

The date published immediately after an anomaly is nearly always optimistic. The one published after the corrective action is defined is usually roughly right.

Sources: NASA and Phys.org. Analysis ours.