The C-27J
Spartan.
A detailed aircraft project for X-Plane 12, built around considered modelling, connected systems, and a cockpit experience where the details have purpose.
Development by Adrianas
A transport aircraft defined by purpose.
Form, function, and material.
The aircraft is more than a silhouette. Proportions, panel construction, access doors, antennas, propeller assemblies, landing gear, cockpit geometry, and surface materials each contribute to the final impression. Lighting and animation should reveal those details naturally, while cockpit layout and visibility should make the aircraft feel designed around its crew.
Modelling priorities will be guided by reference quality and the importance of each feature to the complete aircraft — from the overall shape down to the details visible at close range.
Not a collection of features.
An aircraft that works together.
A control input should lead to a system response. That response should affect the relevant indications, and those indications should help the pilot understand the aircraft. This cause-and-effect approach guides the planned systems architecture, from engine behaviour and electrical power to avionics and pilot tools.
Connected logic, from the controls to the cockpit.
The development focus is on relationships between systems, not isolated animations. Aircraft state, pilot input, equipment availability, and cockpit indications should remain consistent with one another.
Flight dynamics
Consistent control response, trim, stability, and handling across speed, weight, and configuration. Repeated test profiles help evaluate take-off, climb, approach, landing, and ground behaviour.
Engine & propeller behaviour
Power inputs, engine response, propeller behaviour, acceleration, and climb performance should influence one another. Start-up and shutdown are treated as sequences with meaningful states.
Electrical power
Power sources and distribution determine which equipment can operate. A switch requests a change; the system checks conditions, updates its state, and communicates the result.
Fuel, hydraulics & environment
System dependencies, quantities, pressures, control states, and indications are researched as connected functions, with implementation guided by suitable references.
Navigation & guidance
Route data, active legs, selected modes, and displayed information should agree. Where guidance functions are implemented, transitions and mode indications should be predictable.
Warnings & fault states
Cautions and warnings should arise from defined conditions. Where supported by references, abnormal states should have coherent consequences and clear cockpit indications.
Make the indication mean something.
When an aircraft system changes state, the effects should be visible where the pilot expects them. The objective is a coherent simulation in which the cockpit communicates what the aircraft is doing.
Conditions first. Response second.
An electrical component should depend on available power. An engine-start sequence should progress through defined states as the simulated engine responds. A warning should be triggered by an underlying condition, not by a timer or a button animation.
The same principle applies to fuel, hydraulics, environmental controls, landing gear, flaps, and avionics. The implementation will be built in testable layers, with assumptions documented and behaviour checked against reliable references wherever possible.
Full specifications
A closer look at the planned aircraft systems, their logic, and the tools that will support the pilot. This is a development profile: feature scope will evolve as research and implementation progress.
Main developer · Adrianas
Primary flight information: attitude, airspeed, altitude, vertical speed, heading, and relevant flight-mode information according to the cockpit implementation.
Engine and system indications: engine parameters, configuration status, cautions, warnings, and synoptic information tied to aircraft state.
Display consistency: indications should reflect the state of the underlying system rather than act as decorative screens.
Route construction: route entry and review, waypoint sequencing, direct-to functions, leg information, and procedure support where data and interfaces permit.
Route integrity: identify missing waypoints, invalid entries, and discontinuities before activation. Make the active leg and next waypoint clear to the pilot.
Navigation data: investigate compatible simulator navigation sources and flight-plan formats. Database and procedure support depends on compatibility and applicable licensing.
Guidance integration: route data, navigation display, and implemented guidance modes should use consistent flight-plan state.
Mode logic: research appropriate guidance functions before implementation. Clearly distinguish selected modes from active modes where applicable.
Transitions: engagement, disengagement, and mode changes should have predictable results and appropriate indications.
Flight director & autopilot: commands and indications should remain consistent with aircraft state, pilot inputs, and available simulator interfaces.
Electrical: power sources and distribution determine equipment availability; switches request actions while the system checks the necessary conditions.
Engine start: a sequence of meaningful states with changing indications as the engine responds, not an instant transition from off to running.
Fuel, hydraulics & environment: investigate dependencies, quantities, pressures, and control states using reliable references.
Warnings and failures: where feasible and documented, define triggering conditions, indications, and reset or recall behaviour.
Exterior: aircraft proportions, panel construction, access panels, antennas, landing gear, propellers, and material variation guided by references.
Cockpit: considered geometry, readable labels, visibility, instrument depth, and consistent interaction points.
Animation & audio: moving components, lighting, and sound should respond to relevant aircraft state wherever technically supported.
One workspace for the whole flight.
A future EFB designed around flight preparation, aircraft setup, useful performance tools, and post-flight records — with an interface that complements the aircraft rather than feeling like a separate generic app.
Take-off performance
Explore calculations using mass, configuration, runway length and slope, elevation, temperature, wind, and runway condition when reliable data is available. Inputs, assumptions, units, and limitations should remain visible alongside results.
Landing performance
Estimate landing distance using arrival mass, runway and weather inputs, and relevant configuration. Missing or uncertain inputs should be made explicit instead of hidden behind a single number.
Flight planning & FMS transfer
Review routes, waypoint order, alternates, and discontinuities. Investigate importing, exporting, or copying compatible flight-plan data to and from the simulated FMS, with validation and pilot confirmation before changes are applied.
Loading, balance & fuel
Plan cargo and fuel loading, calculate total mass and centre of gravity where the necessary aircraft data is available, and compare planned fuel with simulator values as the flight progresses.
Checklists & aircraft references
Keep interactive checklists, limitations, procedures, and aircraft documentation organised for quick access. Where practical, checklist steps may reflect whether relevant simulated conditions are met.
Logbook & post-flight report
Record completed simulator flights with date, route, airports, block and airborne time, distance, fuel used, maximum altitude, available landing metrics, and pilot notes. Review and export a personal flight history.
Live aircraft information
Investigate supported simulator interfaces so selected EFB pages can reflect aircraft state, route progress, fuel values, and flight details where reliable data access is available.
Performance tools are intended for simulation use. Their reliability depends on suitable reference data, documented methods, and validation; they will not be represented as approved real-world operating data.
Refined through research and testing.
A complex aircraft is developed in layers: establish the foundation, connect systems, evaluate the result, and revisit earlier work when changes introduce new interactions.
Research & specification
Gather references, define scope, record assumptions, and separate verified information from areas that need further investigation.
Aircraft foundation
Establish the aircraft structure, baseline flight model, cockpit layout, and core configuration before expanding into complex features.
Systems implementation
Connect pilot inputs, system state, and cockpit indications through logic that can be tested and maintained.
Flight evaluation
Use repeatable scenarios across take-off, climb, cruise, descent, approach, landing, and ground operations to identify issues.
Visual & audio refinement
Refine materials, lighting, animation, sound, and cockpit interaction while preserving performance and consistency.
Regression & release checks
Re-test key scenarios after changes, document limitations, and communicate clearly what is implemented and what remains in development.
Every detail has a purpose.
From the exterior silhouette to the logic behind a cockpit indication, the work is guided by one principle: the parts should come together as one aircraft.