Investigator guide
How an occurrence moves through SeyAero
This is the platform told as a single investigation, from the moment a report reaches you to the moment you sign something a hostile expert will read. Follow it in order the first time; after that, jump to the stage you are in. Each stage says what to do, where to do it, and the mistake that stage tends to produce.
- 01
T+0 — first fifteen minutes
Open the occurrence file
A report reaches you: an aircraft is overdue, or a separation event has been filed. Before anything else, the investigation needs a container with a datum. Create the case, give it your own reference, and record the last confirmed position and time. Every downstream product — drift, range envelope, search sectors — is anchored to that single datum, so note where it came from.
Case filesCreate the occurrence file and set the datumTeamInvite the team; roles are scoped Lead / Analyst / Observer / AuditorWatch out — If the last position is a secondary-radar return of doubtful quality, say so in the fix confidence. An overstated datum produces a confident and wrong search field.
- 02
T+1h — evidence intake
Feed the file everything you have
Six intake surfaces write to one timeline: flight states, recorder parameters, meteorology, ground and witness facts, voice and media, and exhibits under custody. You do not need all of it to start — the case overview shows which classes are still empty and what each one would unlock. Work the checklist top-down; it is ordered by how much each class narrows the answer.
Flight statesRadar, ADS-B and recorder-derived positionsVoice & mediaCVR/ATC transcription and document OCR, time-alignedFiles & custodyExhibits hashed into the tamper-evident chainWatch out — AI transcription and OCR are drafting aids. Nothing they produce enters the record until you confirm it — the platform keeps the machine draft and your confirmation as separate events.
- 03
T+3h — reconciliation
Reconstruct the sequence
The reconstruction view fits a trajectory to the state vectors and lays voice events, parameter excursions and witness observations on the same time axis. Where sources disagree, both are drawn and the residual is quantified rather than smoothed away. This is where a timeline contradiction — a call made after an event that supposedly silenced the crew — becomes visible in seconds instead of days.
ReconstructionFitted track, energy state and source disagreementSeparationClosest-point-of-approach geometry for near-miss workMethodologyWhat the fit assumes and where it failsWatch out — Record hypotheses as you form them. The platform tracks which evidence supports, contradicts or has yet to be tested against each one — that ledger is what keeps an investigation from anchoring early.
- 04
T+4h — the search prior
Localise a missing airframe
From the datum, a Monte Carlo ensemble of end-of-flight trajectories is propagated within the aircraft's performance envelope, then drifted through the supplied current and wind field to the present hour. The output is a probability density with confidence contours, split into a seabed field and a floating-debris field, and a ranked list of sectors ordered by probability mass per unit search area — the order to task assets in.
Wreckage analysisRun the engine, read the ranked sectorsValidationNine historical hull losses, all contained in the 90% contourWatch out — Record every completed sweep, including the fruitless ones. Negative effort is evidence: it re-weights the field Bayesianly, pushing probability out of swept water and into what remains.
- 05
T+1d — the product
Sign, disclose, defend
When you publish, the report is signed over its own content and over the evidence manifest at the moment of signature. Any later alteration to either breaks the chain and is visible to anyone holding the document. Disclose the methodology pack alongside it; the reproducible validation pack lets a counterparty re-run the benchmark server-side and byte-compare it to the published digest.
Case overviewSign the report and export the custody manifestReproducible packOne-click third-party verificationRegulatory positionWhere SeyAero sits under ICAO Annex 13Watch out — SeyAero is decision support. Findings, causes and safety recommendations remain the sole province of the investigating authority.
Where everything lives
Language used in the outputs
- Datum
- The last confirmed position and time. The anchor for every spatial product in the case.
- Probability field
- A density over the surface, not a point. Read the sectors, never the peak pixel.
- Contour
- The 50/75/90% lines enclose that share of the total probability mass.
- Negative effort
- A completed sweep that found nothing. Evidence, and it re-weights the field.
- POD
- Probability of detection for a sweep, given the asset, sea state and target size.
- Custody chain
- Hash-linked record of every evidence event. Breaks visibly if tampered with.
