Jump to content

Recommended Posts

Posted

Landing Monitor and Flare Analysis : Xplane 12.4+ & FlywithLua NG

View File

Landing Monitor XP12 — Version 1.0

Advanced landing analysis for X-Plane 12

Landing Monitor XP12 is a FlyWithLua NG script designed to analyze every phase of a landing, from the final seconds of the approach to the runway rollout.

The script displays key flight parameters in real time, automatically detects touchdown and the runway in use, calculates a landing score, saves results to a CSV file, and generates a complete graphical analysis of the flare and rollout.


Main Features

Configurable real-time HUD

The compact HUD can display:

  • total acceleration GTOT;
  • GX, GY, and GZ acceleration components;
  • maximum recorded acceleration values;
  • IAS, TAS, and Ground Speed;
  • pitch, roll, angle of attack, and crab angle;
  • thrust, lift, weight, and effective drag;
  • Lift/Weight and Thrust/Drag ratios;
  • vertical speed and data from the latest landing.

Each item can be enabled or disabled individually from the Settings window.

Complete landing analysis

After touchdown, Landing Monitor calculates:

  • landing rate in ft/min;
  • vertical kinetic energy in joules and kilojoules;
  • Peak G;
  • pitch, roll, IAS, and angle of attack at touchdown;
  • crab angle;
  • bounce count;
  • ground speed;
  • wind, headwind, and crosswind;
  • distance from the runway threshold to the touchdown point;
  • lateral deviation from the runway centerline;
  • heading and track errors;
  • flare height, duration, and distance;
  • final landing score and landing quality.

The runway is detected automatically from X-Plane’s apt.dat data. The runway database is cached to improve startup time and can also be rebuilt manually from the Settings window.


Robust Flare Detection

Flare analysis begins below approximately 50 ft. The script records the final approach at 20 Hz, then analyzes the complete sequence after touchdown.

The beginning of the flare is defined as the first segment that meets all of the following conditions:

  • longitudinal control input rises for at least 0.33 seconds;
  • nose-up control input reaches at least 12.5%;
  • total control-input increase is at least 3 percentage points;
  • no significant control-input decrease occurs during the segment;
  • aircraft pitch increases during the same period;
  • total pitch increase is at least 0.10°.

Small tolerances are applied so that normal DataRef noise does not reject a valid flare. The average control-input slope is also calculated and displayed for reference.


Flare & Rollout Analysis Graphs

The analysis window displays five graphs:

  • vertical speed;
  • longitudinal joystick input;
  • aircraft pitch;
  • radio altitude;
  • lateral deviation from the runway centerline.

The FLARE and TOUCHDOWN markers make it easy to visualize the exact timing of the landing sequence.

The first four graphs cover the period from 50 ft radio altitude to two seconds after touchdown. The rollout graph starts at touchdown and continues until 30 kt or until a rapid runway exit is detected.

Lateral deviation values remain in actual metres in all text, calculations, scoring, and CSV output. Only the visual amplitude of the plotted curve is reduced to make the graph easier to read.


Automatic Opening After Landing

Once the landing result has been finalized, the result and analysis windows remain ready in memory.

When the aircraft is on the ground and the parking brake reaches at least 50%, Landing Monitor automatically opens:

  • the landing result and score window;
  • the Flare & Rollout Analysis window.

This automatic opening occurs only once per landing. Both windows can still be reopened manually from the FlyWithLua menu. The script reads two parking-brake DataRefs to improve compatibility with different aircraft.


Landing Score

Each landing receives a score between 0 and 100.

The score starts at 100 points, then penalties are applied for:

  • runway-centerline deviation;
  • flare-to-touchdown distance;
  • crab angle;
  • Peak G;
  • landing rate.

The scoring system is designed to reward overall landing technique and runway alignment, rather than focusing only on achieving the lowest possible touchdown rate.


Settings

The Landing Monitor Settings window allows you to:

  • choose which real-time parameters are displayed in the HUD;
  • choose which landing results are shown;
  • select the CSV separator: comma, semicolon, or tab;
  • view the runway database status;
  • manually rebuild the runway database;
  • select a predefined HUD position;
  • use custom screen coordinates;
  • reset the HUD position to Middle Left.

Display settings do not affect calculations, scoring, graph recording, or CSV data.


CSV Export

Each landing is automatically added to an aircraft-specific CSV file.

The file includes the main touchdown parameters, runway information, flare data, wind, bounce count, and final landing score. The separator can be selected from the Settings window.


Installation

Requirements

  • X-Plane 12
  • FlyWithLua NG

Installation procedure

Copy the Lua file into:

X-Plane 12/Resources/plugins/FlyWithLua/Scripts/
 

Restart X-Plane or reload the FlyWithLua scripts.

During the first installation, Landing Monitor automatically searches for X-Plane’s apt.dat files, builds the runway database, and creates a cache file for future startups.


Available Commands

From:

Plugins → FlyWithLua

you can:

  • open the compact HUD;
  • open the detailed display;
  • open the Settings window;
  • open the Flare & Rollout Analysis window;
  • reset the HUD position;
  • rebuild the runway database.

These commands are registered automatically when the script is loaded.


Compatibility

Landing Monitor XP12 is designed for X-Plane 12 with FlyWithLua NG.

Some functions may depend on the DataRefs provided by each aircraft, especially parking-brake position, aerodynamic forces, and flight-control inputs.

 

 


 

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...