cmbaviator

VATSIM Real Data v1.0 is a compact X-Plane 12 plugin that displays live VATSIM and xPilot information directly inside the simulator, including radio status, nearby frequencies and the 10 closest aircraft.
Full description
VATSIM Real Data v1.0 adds a compact, customizable VATSIM information window to X-Plane 12.
The plugin integrates with xPilot and displays your current connection status, callsign, nearby traffic, COM frequencies, microphone activity, SELCAL information and live VATSIM feed status.
It also shows the five nearest VATSIM ATC frequencies and the ten closest aircraft, with useful flight and proximity information presented in a single readable table.
Main features
xPilot connection status and callsign TX and RX indicators COM1 and COM2 frequencies Active station callsigns Microphone level meter SELCAL status Five nearest VATSIM ATC frequencies Ten nearest VATSIM aircraft Aircraft callsign and type Departure and destination airports Bearing and horizontal distance Relative altitude Ground speed and altitude Reported COM1 frequency Automatic window resizing Fully configurable display from the X-Plane plugin menu Automatic settings saving Compact opaque interface designed for cockpit use Traffic proximity colors
Nearby aircraft are color-coded using horizontal and vertical separation:
Red: less than 3 NM and less than 1,000 ft vertical separation Amber: less than 6 NM and less than 2,000 ft vertical separation Green: all other traffic This feature is intended as a situational-awareness aid only. It is not a certified TCAS system.
Customization
Display options can be changed directly from:
  Plugins > VATSIM Real Data   Sections, aircraft columns, aircraft count and frequency count can be enabled or disabled without restarting X-Plane. The window automatically adjusts its size and saves the selected settings.
Installation
Copy the complete folder:
VatsimDataWindow into:
X-Plane 12\Resources\plugins\ The final structure should be:
X-Plane 12\Resources\plugins\VatsimDataWindow\64\win.xpl Restart X-Plane after installation.
Requirements
X-Plane 12 Windows 64-bit xPilot Internet connection for live VATSIM data Disclaimer
 
VATSIM Real Data is an independent community plugin. It is not affiliated with, endorsed by or officially supported by VATSIM, xPilot or Laminar Research.

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.
 
 

Credits and acknowledgements
Special thanks and full credit go to @Matchstick creator of the original CJ525 N1 Calculator.
The N1 calculation system developed by Matchstick provided the original foundation for determining the applicable CJ525 N1 limits according to flight phase, altitude and temperature.
This calculation logic was adapted and incorporated into the CJ525 Human Throttle package. It supplies the N1 MAX targets used by the plugin during Takeoff, Climb, Cruise and Go-Around.
The Human Throttle project adds its own features around this calculation system, including:
human-style thrust-lever management in N1 MAX mode; automatic takeoff engagement; return-flight rearming; flight-phase detection; conventional PI-D IAS HOLD; predictive N1 protection; automatic approach disconnection; Original Matchstick CJ525 N1 Calculator:
https://forums.x-pilot.com/files/file/1635-cj525-n1-calculator/
The original N1 calculation work remains credited to Matchstick. The integration into CJ525 Human Throttle does not imply that Matchstick is responsible for, associated with, or endorses the additional autothrottle functions developed in this plugin.
 
CJ525 Human Throttle
Current version : 0.7.0
Installation
Requirements
X-Plane 12 TorqueSim CitationJet 525 FlyWithLua NG+ The included CJ525 N1 performance-table script Installation steps
Close X-Plane. Open the FlyWithLua scripts folder: X-Plane 12/Resources/plugins/FlyWithLua/Scripts/ Remove any older version of CJ525 Human Throttle from this folder. Do not keep several controller versions active at the same time, as they may create duplicate commands or attempt to control the thrust levers simultaneously.
Copy the main controller into the Scripts folder: CJ525_Human_Throttle_v0.7.lua Copy the required CJ525 N1 performance-table script into the same folder. The controller requires this script to calculate and publish the applicable N1 MAX target for Takeoff, Climb, Cruise and Go-Around.
 
Start X-Plane 12 and load the TorqueSim CitationJet 525. FlyWithLua should load the scripts automatically.
First startup
When the plugin starts for the first time, it uses its default settings:
Takeoff-to-Climb transition: 500 ft radio altitude Automatic approach disconnect: 500 ft radio altitude Touchdown flap assist: disable The settings file is created when the settings are saved:
CJ525_Human_Throttle_settings.cfg This file is stored in the same FlyWithLua Scripts folder.
Command assignment
The following commands can be assigned to keyboard keys, joystick buttons or hardware controls from the X-Plane control settings:
FlyWithLua/CJ525_Human_Throttle/toggle_AT FlyWithLua/CJ525_Human_Throttle/AT_ON FlyWithLua/CJ525_Human_Throttle/AT_OFF FlyWithLua/CJ525_Human_Throttle/N1_MAX FlyWithLua/CJ525_Human_Throttle/IAS_HOLD FlyWithLua/CJ525_Human_Throttle/toggle_IAS_HOLD Automatic takeoff engagement
No manual engagement is required during a normal takeoff when all conditions are met.
The system automatically engages in N1 MAX mode when:
The aircraft is in the TAKEOFF phase The N1 performance calculator is in Takeoff mode The published N1 MAX target is valid The highest engine N1 rises above 70% At exactly 70.0% N1, the system remains disengaged.
After landing, the next takeoff cycle is automatically rearmed when the aircraft is on the ground and the highest engine N1 decreases to 60% or below.
Checking the installation
After loading the aircraft, verify that:
FlyWithLua reports no script errors; the CJ525 Human Throttle monitor appears; the N1 MAX value is displayed; the commands are visible in the X-Plane control settings; the system automatically engages above 70% N1 during takeoff. Troubleshooting
When the plugin does not load:
Check the FlyWithLua debug file for errors. Confirm that only one version of the controller is installed. Confirm that the N1 performance-table script is present. Confirm that the loaded aircraft is the TorqueSim CitationJet 525. Reload all FlyWithLua scripts or restart X-Plane.  
 
Description :
 
CJ525 Human Throttle adds thrust-management assistance to the TorqueSim CitationJet 525 in X-Plane 12.
The plugin is built around two complementary operating modes: N1 MAX and IAS HOLD.
Human-style N1 MAX management
N1 MAX mode is designed to simulate a Pilot Monitoring manually adjusting the thrust levers.
Instead of instantly placing the throttles at a calculated position, the system observes the engine N1 values and progressively moves both thrust levers toward the published N1 limit for the current flight phase.
The simulated Pilot Monitoring:
adjusts the thrust levers through deliberate, progressive movements; pauses between corrections to observe the engine response; reduces the correction size when approaching the target; monitors both engines and uses the highest N1 when necessary; prevents the published N1 MAX limit from being exceeded; adapts the target to Takeoff, Climb, Cruise and Go-Around performance data. During takeoff, N1 MAX can engage automatically when the highest engine N1 rises above 70%.
After landing, the system rearms when the aircraft is on the ground and N1 decreases to 60% or below. This allows automatic engagement on a return flight without reloading the Lua script.
 
 
 
Conventional IAS HOLD baseline
IAS HOLD reads the selected airspeed directly from the CitationJet cockpit speed selector and controls the thrust levers to capture and maintain that speed.
In the current version, IAS HOLD behaves like a conventional real-time autothrottle. A continuously evaluated PI-D controller applies small thrust corrections according to:
the difference between selected and actual IAS; the current IAS trend; the aircraft’s vertical flight condition; the active gain schedule; the available N1 margin. This conventional control law was intentionally developed and validated first to establish a stable and reliable autothrottle baseline.
IAS HOLD currently uses three control schedules:
TRANSITION for larger speed changes and captures; LEVEL for stabilized flight close to the selected IAS; BASELINE for climb, descent and other non-level conditions. N1 MAX protection always has priority over IAS HOLD commands.
Future humanisation of IAS HOLD
Future versions are planned to make IAS HOLD behave more like a human Pilot Monitoring operating the thrust levers.
The development objective is to progressively introduce:
more deliberate throttle movements; observation periods between corrections; fewer continuous micro-adjustments; reaction timing based on aircraft energy trends; more natural anticipation during speed and altitude changes; less mechanical control behavior while preserving the validated N1 protections. Version 0.7 should therefore be considered the validated conventional IAS autothrottle baseline, while N1 MAX already follows a more human-style Pilot Monitoring logic.