Hi Everyone,
We’ve introduced a new flight analysis system to give clearer, more meaningful feedback on how flights are flown — particularly during the approach phase.
This is not a scoring or penalty system. It is designed to show what the aircraft was doing, and where things may have become less stable or more difficult than intended.
What the system evaluates
The system looks at the entire flight profile, not just the landing:
- Flight phase (Taxi climb, cruise, descent, approach)
- Airspeed and how it changes over time
- Aircraft configuration (flaps, gear)
- Stability before landing
- Landing outcome
The focus is on how the approach was managed, not just how it finished.
Core principle
At each stage of flight, the aircraft is expected to be within a reasonable operating profile.
If something sits outside that expected profile, it may be flagged to help highlight:
- Excess energy (too fast)
- Late configuration
- Instability developing on approach
- Taxi speed, common faults here is taking off without landing lights on.
Approach phase (key area)
Most of the analysis is focused on the approach, as this is where stability matters most.
The aircraft enters approach phase either:
- Automatically (near the DECEL point), or
- Manually (when selected by the pilot)
Once in approach phase, the system expects to see:
- A steady reduction in speed
- Gradual configuration (flaps and gear)
- Transition toward final approach speed
Speed expectations
Typical pattern the system looks for:
- Below ~220 kt → early approach phase
- Around 200 kt → initial configuration begins
- Around 180 kt → further configuration / base to final
- Final approach → speed stabilised near VAPP
If the aircraft remains fast (e.g. above ~220 kt) after entering approach phase, it will be flagged as a high-speed approach, as this usually indicates excess energy being carried into the approach.
Energy management
The system doesn’t just look at speed — it also looks at how quickly the aircraft is slowing down.
If speed is not reducing in line with distance to the runway, this can be flagged as:
- Energy being carried too far into the approach
- Increased likelihood of late corrections
Configuration (flaps and gear)
Configuration is treated as part of controlling the aircraft’s energy.
The system expects to see configuration progressing alongside speed reduction:
- Flaps used progressively as speed reduces
- Gear deployed in the later stages of the approach
- Landing configuration achieved before final stabilisation
If configuration is delayed or happens very late, it may be highlighted as increasing approach workload and instability risk.
Stabilised approach check
Closer to the runway, the system checks whether the approach is stabilised.
Typical reference points:
- Around 1000 ft AGL (IMC)
- Around 500 ft AGL (VMC)
At this stage, the system looks for:
- Speed close to final approach speed
- Aircraft in landing configuration
- A steady, controlled descent
If significant corrections are still happening late, it may be flagged as an unstable approach.
Landing vs approach
A key point:
A smooth landing does not always mean the approach was stable.
It is possible to:
- Carry excess speed
- Configure late
- Make late corrections
…and still achieve a reasonable touchdown.
The system highlights the approach leading up to the landing, so you can see where things may have been rushed or compressed.
How results are presented
Flags are grouped to give context rather than isolated warnings.
You may see:
- High-speed approach
- Late configuration indicators
- Unstable approach
These are based on a combination of factors rather than a single data point.
Severity levels
- Advisory – small deviation from the expected profile
- Caution – developing instability or increased workload
- Warning – outside the expected approach envelope
These are there to guide interpretation, not to penalise.
What this means for you
To stay within a stable profile:
- Avoid entering approach phase while still fast
- Begin reducing speed earlier if required
- Use configuration progressively
- Aim to be settled and stable before the final stages
Final note
This system is there to support you, not to judge.
It provides visibility into your approach so you can:
- Understand what happened
- Identify where things became busy
- Improve consistency over time
Feedback is welcome, and the system will continue to be refined based on what you see in your reports.
Many Thanks,
Mark.
