Skip to content
fr

Airlines and flight safety

FDM data and the ASR on the same timeline.

Flight data monitoring (FDM) tells you what crossed a threshold, to the second. The pilot’s report tells you what they perceived and why they carried on. Read apart, they leave a gap in the middle. PHASE puts both on one axis and shows how the situation built up.

Open the FDM/ASR demoSuggest an event

What a flight safety office deals with

FDM events without the why

A +15 kt speed exceedance at 750 ft, a sink rate over the limit, a 2.15 g touchdown. The data gives you what, when and how much. It does not tell you what the crew knew, or what else was being asked of them at that moment.

ASR reports without the timing

The narrative gives the reasons: late vectors, gusts, end of a long duty, “recoverable before 500 ft”. But its timing is approximate. You cannot tell when each factor came into play.

Two documents read one after the other

The analyst rebuilds the sequence mentally, and feedback to crews ends up as a list of exceedances. What held, the defence that did work, drops out of the story.

What PHASE brings

1

One timeline

Every fact keeps its source: the FDM trace, the ASR narrative, or both. Measured times and times known only by their order are kept distinct, never blended.

2

What the crew knew, moment by moment

An aircraft state nobody has noticed yet is drawn with a dashed outline. The cursor shows what was available on the flight deck, and what was not yet.

3

What was still holding

Protections and recoveries stay on the chart. A continued approach is read with its margins, not just its exceedances.

4

From event to training

An EBT reading of the event, a scenario to replay in the simulator, the questions to ask the crew. The debrief is about the case, not the people.

Demo

An unstabilised approach, read from both sources.

A fictitious case: night arrival on the fourth sector, vectors shortened by ATC, rain and gusts. At 1,000 ft the speed is still above the criterion; the pilot judges the path recoverable and continues. The FDM event and the ASR sit on one chart, then become a training proposal.

Open the FDM/ASR demo
PHASE chart : Unstabilised approach continued, A320, flight XA 342
InterceptInterceptFinal approachFinal approachTouchdownTouchdownPF: perceived schedule pressure, reportedPF: end-of-duty fatigue, reportedWorkload management: speed reduction started latePM monitoring: not documentedPF: decision to continue, gate moved to 500 ftEnergy management: speed not brought back to targetFlaps 3 at 1,500 ftLate thrust reduction, nose loweredFlare and touchdown, pitch 2.2°Approach continued outside criteria at 1,000 ftHigh and fast at localiser interceptSpeed above targetRate of descent 1,150 ft/min at 900 ftFirm landing: +2.15 gWind 240/18 kt, gusting 28 ktModerate rain, wet runway, nightVectors shortened at a late stageFourth sector of the duty, night arrivalT−3:30T−3:00T−2:30T−2:00T−1:00T−30 sT01,500 ft1,500 ft1,000 ft, stabilisation gate1,000 ft, stabilisation gate500 ft500 ftTouchdownTouchdownT−1:20

What we can do with you

Analyses are carried out on request, on de-identified documents, under terms agreed with you. Nothing is published.

  • Analysis of one of your events

    From your FDM event and the matching ASR: a chart, a record for every fact, an EBT reading and a training proposal.

  • A review of a series of events

    Several comparable events read through time, to bring out recurring patterns and defences that come into play late.

  • A presentation session

    With your flight safety office or training management: the demo first, then a case of your choosing.

Frequently asked questions

Is a recent event on your mind?

Describe it in a few lines, without names or identifying data. The founder will get back to you with a way to read it.

Suggest an event