Search the Community
Showing results for tags 'landing monitor landing rate flare analysis'.
-
Version 1.0.3
14 downloads
Landing Monitor XP12 – Version 1.0.3 Landing Monitor XP12 is a complete landing-analysis tool for X-Plane 12, designed to provide detailed touchdown, flare and rollout feedback after every flight. The plugin records the final approach from approximately 50 ft radio altitude, analyses the pilot’s longitudinal control input, detects the pre-flare and flare phases, identifies the landing runway, measures centerline performance and calculates a detailed Landing Score. It is intended for flight-simulation analysis and training. Main Features Real-Time Flight Data A configurable compact HUD displays: Total, longitudinal, lateral and vertical acceleration Maximum total acceleration IAS, TAS and groundspeed Pitch, roll, angle of attack and crab angle Thrust, drag, lift and aircraft weight Lift-to-weight and thrust-to-drag ratios Landing Monitor status Current script version Every item can be enabled or disabled independently. Detailed Touchdown Analysis After landing, the plugin records and displays: Landing rate Peak G Vertical impact energy Touchdown IAS and groundspeed Pitch, roll and angle of attack Crab angle Heading and track error Headwind and crosswind components Bounce count Runway and airport identification Distance from the runway threshold Signed centerline deviation in metres and feet Landing Score and Landing Quality Peak G is captured during the first 0.75 seconds following initial contact. Relative Flare and Pre-Flare Detection Version 1.0.3 introduces a fully relative flare-detection system based only on the filtered longitudinal joystick-deflection curve. The algorithm does not require a fixed joystick percentage and does not use pitch, vertical speed or angle of attack to validate the flare. FLARE is selected from the first ascending control-input phase reaching more than 80% of the maximum filtered joystick deflection recorded during that landing. PRE-FLARE is selected from the last earlier ascending phase reaching more than 50% of the same maximum. A relative slope check refines the effective beginning of the flare and prevents a long, nearly flat control-input section from placing the marker too early. This relative method allows the detector to adapt to aircraft requiring very different control-input amplitudes. Flare & Rollout Analysis Graphs The analysis window provides synchronized graphs for: Vertical speed to touchdown Filtered longitudinal joystick deflection Aircraft pitch Radio altitude Lateral deviation during rollout The graphs include clearly identified: PRE-FLARE marker FLARE marker TOUCHDOWN marker Airport and runway Detection thresholds and phase information Vertical speed and joystick data stop at touchdown, while pitch and radio-altimeter data continue for two additional seconds. Rollout deviation continues until 30 kt or until a runway exit is detected. Accurate Runway Selection The runway database respects the priority order defined in scenery_packs.ini. For each airport, the first enabled scenery providing physical runway data is retained, while lower-priority duplicate definitions are ignored. At touchdown, the plugin uses a geographic runway index and performs exact geometry calculations on no more than 24 nearby candidates. This avoids scanning the complete global runway database during landing and helps ensure that custom-airport geometry is used correctly. Revised Landing Score The Version 1.0.3 Landing Score is based on four categories: Centerline deviation: 30 points Flare or pre-flare score distance: 25 points Wind-aware crab angle: 20 points Peak G: 25 points Full centerline credit is awarded inside ±1 metre. The accepted crab-angle range changes according to the crosswind component: Crosswind below 5 kt: ±1° Crosswind from 5 to 15 kt: ±2° Crosswind above 15 kt: ±3° Landing Quality is based on Peak G rather than vertical speed. Landing rate remains displayed and logged but does not affect the score. Automatic Post-Landing Display When enabled, applying at least 50% parking brake after a finalized landing automatically opens: Landing Monitor Flare & Rollout Analysis The trigger reads two parking-brake DataRefs, stores the detected state and retries the deferred window-opening request until both windows are confirmed. The automatic display can be disabled in Settings without disabling monitoring, scoring, graph recording or CSV export. Independent Windows and Persistent Settings Three windows are controlled independently: Compact Real-Time HUD Landing Monitor Flare & Rollout Analysis All windows remain closed when X-Plane or FlyWithLua starts. Monitoring continues in the background. Display choices, HUD position, custom coordinates, CSV separator and the automatic parking-brake option are saved between sessions. Automatic CSV Logging Each completed landing is automatically saved to a per-aircraft CSV file. Version 1.0.3 uses: LandingLog_v9_<separator>_<aircraft>.csv The log includes touchdown data, runway and wind information, flare and pre-flare measurements, score-distance information, Peak-G-based Landing Quality and the final Landing Score. Requirements X-Plane 12 FlyWithLua NG A supported 64-bit operating system Write permission in the FlyWithLua Scripts folder Installation Close X-Plane 12. Copy: LandingMonitorFlareAnalysis_XP12_v1.0.3.lua into: X-Plane 12/Resources/plugins/FlyWithLua/Scripts/ Remove or archive previous Landing Monitor Lua versions. Start X-Plane. Open the FlyWithLua menu to access the Landing Monitor windows, settings and commands. When updating from an older version, the runway cache may be rebuilt automatically. Rebuild the runway database manually after changing scenery_packs.ini or installing a new airport scenery. What Is New in Version 1.0.3 New relative FLARE and PRE-FLARE detection Filtered joystick-deflection analysis Complete approach history retained below approximately 50 ft Effective flare-onset refinement using relative slope PRE-FLARE measurements and score-distance calculation Scenery-priority runway selection Version 2 runway cache Geographic runway index and limited local candidate search Peak-G-based Landing Quality Revised Landing Score Wind-aware crab-angle tolerance Full centerline credit inside ±1 metre Simplified filtered-joystick graph Script-version labels in all main windows Improved parking-brake automatic window opening Updated LandingLog_v9 CSV format Important Notice Landing Monitor XP12 is a flight-simulation analysis tool. It is not certified avionics and must not be used for real-world flight operations, aircraft maintenance or regulatory compliance. -
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. Submitter cmbaviator Submitted 07/26/2026 Category Plugins and Utilities
