Talk:Orbit

Development and editorial material moved from the article — 27 October 2026

The following original passages were moved or rewritten to keep Orbit focused on operating in Vieneo. They are preserved here as development history, editorial context or source material, not as current operating instructions. Player-facing limits and controls are retained in the article where applicable.

Source: Orbit, revision 5052. The excerpts below preserve the original wikitext, including any obsolete statements and links.

'''About the illustrations:''' These are labeled scenario renders from the implemented instrument's layout, orbital planner and guidance code, using synthetic example conditions. They are not screenshots of live flights. Each uses the native 420 × 320 layout enlarged for reading. Example times, fuel and delta-V are not a performance promise for your vehicle. Some dated illustrations use earlier labels (MIN ROUTE ALT, TO GO / USED and ATM PASS) and omit the live MECO estimate; the current readouts are described below.

'''Client versions and limits:''' Orbital adjustment, rendezvous and overflight have executable plans. [[#Surface journey planning|SURFACE PLAN]] remains planning-only for ground and low-atmospheric departures. The [[#Automated entry alpha|automated-entry alpha]] adds '''REENTRY''' execution from orbit to an atmospheric handoff, followed by aircraft guidance and TAS hold. FINAL HOLD captures altitude; runway ILS/VISUAL handoffs retain a descent. With FINAL ILS selected before entry, the aircraft controller continues a steep descent into a descending 3-degree localizer/glideslope intercept. VISUAL continues to the same final geometry, with final approach left to the pilot. Flare and touchdown remain manual. This requires the client with '''ENTRY READY'''; earlier calibration clients show '''REENTRY PLAN / PLAN ONLY''' and support manual REC capture only.

''Older orbital illustrations show ORB1 and DOR-prefixed phases. Static illustrations do not demonstrate the execution blink.''

| Your configured DOR on/off control || Engage or disengage a valid executable plan. SURFACE PLAN stays planning-only. The automated-entry alpha can execute an ENTRY READY reentry; after handoff, the same control cancels its TAS hold.

'''Administrator diagnostics:''' REC and automatic local CSV capture are available only to administrator accounts. Other accounts have no REC row and their DOR flights are not recorded automatically. Losing administrator permission ends an active capture without changing DOR guidance.

Selecting Orbit does not replace or acknowledge [[EICAS]] indications. With EICAS powered and serviceable, its gear, engine, trim and crew-alert indications remain independent of the MFD page. If these disappear only while ORB1 is selected, that is a rendering fault, not evidence that the underlying condition has cleared.

| REENTRY || The surface-arrival objective for an orbital/high-altitude departure, including while docked at a station. Compare direct powered entry with coast-then-entry, ending upstream of the waypoint at the selected HANDOFF altitude and TAS. The automated-entry alpha can execute a qualifying ENTRY READY plan after undocking.

| CURRENT > FINAL || Current AP/PE/e followed by the proposed final orbit after all burns. Older captures say CURRENT > PLAN. This is not the transfer minimum. CURRENT > REQUEST is an editable goal for which no valid plan exists yet.

[[File:Orbit-MFD-rendezvous-min-route-alt-20261016.png|thumb|center|600px|'''Scenario 18: route minimum and final orbit.''' Fresh labeled render from the actual planner/display code. This synthetic rendezvous has a final PE and route minimum both at 118 km. With the 10 Pa advisory threshold, its route minimum is neutral gray; LONG BURN - ESTIMATE and the independent reversal caution remain visible. This is not a live flight, a reconstruction of player telemetry or a guarantee of execution.]]

See the updated blocked-overfly illustration under [[#Overfly atmospheric clearance|Overfly atmospheric clearance]]. It replaces the older example that allowed the same low-periapsis route as a warning-only plan.

* History is collected for every pilot without REC, including manual departure. If observation starts airborne, '''DIST FROM PICKUP (km)''' identifies its origin. Landing, a vehicle/simulator change or a flight-state reset starts a new history. REC is separately restricted to administrators and writes diagnostic files.

For a vacuum orbital objective such as ADJUST ORBIT, '''ASCENT PROFILE REQUIRED''' means that objective has no executable powered launch. Choose '''MODE RENDEZVOUS''' for a complete trip to an orbital target, or '''MODE PARKING ORBIT''' for a separate powered climb ending at a parking orbit. Older clients require manual ascent. Any ordinary vacuum transfer estimate starts from your measured position and velocity; it does not include lift or drag in that predicted path.

There is no hard atmospheric boundary at 75 or 100 km. The planner's warning estimate uses the client's density model and air-relative speed. The 100 km ascent-view transition is a display rule. OVERFLY separately uses 100 km as a minimum clearance policy and also checks dynamic pressure; neither use defines a physical atmospheric boundary.

=== Automated ascent alpha ===

# Select '''MODE PARKING ORBIT''' on DOR when you want to stop at a parking orbit. Set '''ORBIT 200 km MSL''' for the first test; the range is 150–1000 km in 50 km steps.

# In clients with the '''LAUNCH''' row, leave '''LAUNCH AUTO''' selected to arm the recommended departure: engage DOR to await the comparison and its recommended departure. While comparing it shows ARMED / COMPARING LAUNCHES with no thrust or attitude command. After accepting a completed, current, fuel-fitting estimate it shows '''ARMED / LAUNCH WAIT''' and '''LIFTOFF IN''' until departure, then starts VTOL automatically. Choose '''LAUNCH NOW''' for immediate departure instead. Earlier clients without this row launch immediately on engagement. VTOL first lifts approximately level to 100 m AGL, then transitions to a climb using lift and pitch to direct the main engines. '''Retract the gear yourself after liftoff.''' DOR does not operate it.

For administrator accounts, DOR automatically records an executed ascent. A ground RENDEZVOUS keeps the same automatic recording through insertion and the orbital transfer; REC need not be switched on separately. Keep both matching CSV files from OrbitLogs, including ascent commands, the insertion handoff, steering selection and actual engine/RCS response. REC remains available for a continuous flight capture through manual flight and later maneuvers. Use the procedure below when recording a manual profile.

Pickup still needs valid current vehicle/air data and the supported configuration. Engagement is refused above 95% Vne, at 200°C AFT or hotter, or more than 50 km above the selected parking-orbit altitude. Those are controller eligibility limits, not proof that every accepted flight can recover. The ground timing/fuel forecast no longer describes a manually flown departure. A retained ground RENDEZVOUS continues automatically after insertion, using the achieved orbit and original absolute MEET; an infeasible transfer stops with a reason. Standalone PARKING ORBIT ends at insertion. For administrators, automatic mission recording includes the armed wait and launch countdown.

=== Recording an ascent ===
These recording controls require an administrator account.
In clients with '''REC ON (FLIGHT)''', administrators can use REC in every objective, including when '''ASCENT PROFILE REQUIRED''' is displayed. Recording observes the flight; it does not engage DOR, supply an automatic ascent pitch/throttle schedule or change ATC routing. A recording is calibration evidence, not an executable profile loaded into the ship.

# Before takeoff, select the intended station or spacecraft and open DOR. Select '''REC''' with Shift + Up/Down, then press Shift + Left/Right. With no proposed path, the row reads '''REC ON (FLIGHT)'''.
# Fly your normal comfortable ascent using manual controls or appropriate existing Autoflyte modes. Follow ATC headings/fixes and make your normal gear, flap, throttle and pitch changes. There is no required 15-degree or 60-degree test attitude.
# Leave REC on through the thin-atmosphere transition and orbital insertion, including any later DOR maneuver. Changing target, planning controls, VIEW or MFD page does not stop a FLIGHT recording. It remains flight-only even if a plan subsequently becomes available.
# Once established in the intended orbit, turn '''REC OFF'''. Keep both matching '''DOR-N.csv''' and '''DOR-N-plan.csv''' from '''OrbitLogs''' beside the running executable. Note the vehicle, starting load and any unusual weather or ATC interruption when returning the files.

The flight CSV records current mass/fuel, available and delivered thrust, actual pitch/roll/heading, angle of attack, air-relative flight-path angle, radial climb speed, tangential inertial and ground-relative speed, air-data freshness, IAS/TAS, dynamic pressure, AFT, configuration and Autoflyte modes. It distinguishes vehicle attitude from velocity direction. The companion file contains the capture origin and any available current/target trajectory context; '''it contains no invented reference ascent'''. Recording stops on REC OFF, loss of administrator permission, vehicle/simulator state reset, client exit, a file error or the size cap. Copy both files before further tests reuse their slot.

If a proposed path exists when REC starts, the row instead reads '''REC ON (REF)'''. That captures a frozen reference and follows the stop rules under [[#Recording a manual entry test|manual reference recording]]. REF recordings end when the target or planning controls change, or when DOR execution begins.

[[File:Orbit-MFD-adjust-size-msl-20261016.png|thumb|center|600px|'''Scenario 3: circularize using MSL altitude.''' With e = 0, the selected SIZE of 937.0 km MSL matches the final AP and PE. The nearly circular starting orbit needs only a small correction. Fresh labeled scenario render from the instrument code, not a live flight.]]

Orbital pressure advisories trigger above '''10 Pa'''. This operating tolerance applies consistently to current-coast, transfer, target and live DOR pressure checks, including OVERFLY's pressure criterion. [[YSP]] at 118 km produces approximately 6.3 Pa in the existing client density model, so its orbit alone no longer raises ATMOSPHERIC TARGET. The separate red below-100-km warning and OVERFLY minimum altitude still apply. Targets explicitly in atmospheric-flight reference mode still receive a target warning. Fuel, thrust, orbital-direction and finite-burn checks remain separate; this threshold change does not alter station fuel use or simulate heating.

DOR follows the selected executable orbital plan. '''SURFACE PLAN cannot engage DOR''', even when a route says MODEL FIT. [[#Automated entry alpha|REENTRY in the automated-entry alpha]] has a separate powered-entry controller. During ALIGN and active burns of executable orbital plans, DOR steers pitch and yaw with rotational RCS, points the nose along the commanded burn direction for forward main-engine thrust, and rolls wings level relative to Vieneo's local horizon. The existing flight director receives burn pitch/heading targets and a level-roll reference; Orbit adds no separate attitude-command panel. In WAIT/COAST these remain guidance for the next burn, not a direction the ship must hold. Near a vertical burn, the horizon roll reference is ambiguous, so the controller preserves a stable roll orientation. DOR does not turn on the aircraft Autoflyte autopilot to do this.

[[File:Orbit-MFD-dor-align-20261016.png|thumb|center|600px|'''Scenario 19: ALIGN before thrust.''' A fresh, labeled scenario render from the actual executor, attitude controller and instrument drawing code, not a live client screenshot. DOR is engaged, EXEC and ALIGN are in their visible blink phase, and translation commands are held off while the ship turns. START NOW does not bypass alignment.]]

'''ALIGN''' uses rotational RCS before allowing a burn. It captures within 2 degrees with total angular rate below 0.5 degree/second for at least half a second; more than 5 degrees of attitude error or 2 degrees/second of angular rate returns it to ALIGN. The commanded slew rate is limited to 5 degrees/second per body axis, with braking based on available torque. These are Rise control settings, not an Earth aircraft envelope. Small velocity trims below 2 m/s within the same burn phase retain the established nose direction instead of chasing a reversing near-zero vector; bounded translation controls handle those trims.

'''WAIT and COAST allow free attitude control.''' You may turn the ship in pitch, yaw and roll to look around while DOR remains engaged and the route stays armed. DOR does not force an immediate return to the next burn direction. With the controls released, gentle rotational RCS follows the changing local horizon, lowering the nose as a forward-facing ship travels around Vieneo. It preserves your chosen attitude relative to that changing horizon rather than forcing the nose onto the flight path or restoring level roll. This uses measured motion and planet rotation, not an Earth orbit rate or an altitude cutoff.

[[File:Orbit-MFD-dor-powered-recovery-msl-20261016.png|thumb|center|600px|'''Scenario 20: powered recovery remains engaged.''' Fresh labeled render from the actual planner, executor and drawing code. ADJUST ORBIT requests a 500 km circle from a slow suborbital state; the unrelated selected station is not the objective. The negative current PE and red ATM PASS warning describe the unpowered coast. The powered correction passes its separate check. An independent finite-thrust regression with ideal steering and engine spool completes above 419.3 km, despite repeated rejection by the old coast-only guard. Synthetic example, not a live flight or reconstructed player telemetry.]]

''The older illustration above demonstrates the layout, not automatic PASS initialization. The clearance illustration below is a labeled code-generated scenario, not a live-flight capture.''

The pressure estimate uses the client's 3.063 kg/m³ surface density, 7.5 km scale height and a conservative bound on air-relative speed at the lowest point of the checked arc. At orbital speed, this can require clearance higher than 100 km. These are operational planning checks, not a validated heating envelope, drag-integrated trajectory or guarantee of finite-burn performance. Vieneo's nitrogen/sulfur-dioxide/oxygen atmosphere is retained; no Earth heating coefficients or new atmospheric boundary are introduced. The published [[Vieneo]] scale height is 7.5 km, matching the client and server models.

[[File:Orbit-MFD-overfly-clearance-blocked-20261016.png|thumb|center|600px|'''Scenario 17: atmospheric overfly blocked.''' Fresh labeled render from the actual planner and instrument code. A synthetic 905 km orbit requests a 200 km COAST pass in 180 minutes, but the candidate falls to 65.3 km. The red MIN ROUTE ALT 65.3km MSL, atmospheric warning and NO PLAN identify the rejection before engagement; the independent retrograde/reversal caution remains visible. This is not a live client screenshot or a reconstruction of player telemetry.]]

For a ground or low-atmospheric departure, select point B on the normal target instrument. On this page choose MODE '''SURFACE PLAN''', then ROUTE and TRIP while on the ground, or PASS when already airborne. For a departure from orbit or an orbital station, use the [[#Reentry and atmospheric entry|REENTRY]] controls below instead. Docking prevents execution, not planning. SURFACE PLAN remains planning-only after undocking; a qualifying REENTRY plan in the automated-entry alpha can be executed.

| ATM || A powered atmospheric profile, climbing to 20 km MSL, traversing toward B, then descending. Only offered for departures at or below 40 km in this initial model. It is not a simulation of wing-borne cruise.

'''TRIP is the requested travel duration before departure.''' While on the ground with REC off, it stays steady: TRIP 30:00 means a 30-minute journey starting when you depart. Waiting on the ground does not consume that allowance or make the same route require more thrust and fuel. At liftoff the deadline is fixed and the row becomes '''PASS''', counting down to arrival. For administrators, starting '''REC''' also fixes the reference at capture start, even if you are still on the ground; it must not slide forward during a calibration recording. Ending REC while still grounded restores the selected TRIP duration. Landing with REC off also restores duration planning. An already-airborne surface preview uses PASS from the time it is selected.

'''MODEL FIT is not flight clearance.''' The preview uses Vieneo gravity and rotation, the client's 3.063 kg/m³ surface density and 7.5 km density scale height, vehicle main thrust, altitude efficiency, fuel flow, wear and empirical body drag. The published [[Vieneo]] scale height matches the 7.5 km used by both client and server. Cruise at 20 km, the 100 km powered-segment interface and nominal 400 km orbital coast are planning choices, not atmospheric boundaries.

'''PLAN ONLY / ATM HANDOFF''' means the atmospheric stages require separate pilot/Autoflyte operation. SURFACE PLAN provides no automatic mode handoff, takeoff, atmospheric guidance, hover or landing. Orbital REENTRY has its own alpha controller described below. The end-state is an ideal planning endpoint at B, not a landing command. Pressing DOR on a surface preview leaves execution off and plays the Autoflyte disconnect cavalry sound once to acknowledge the refusal. Holding the key does not repeat the sound. Existing executable ADJUST ORBIT, RENDEZVOUS and OVERFLY plans remain separate.

The dated scenario illustrations below use the earlier PASS label before takeoff; current ground previews display TRIP.

File:Orbit-MFD-surface-atm-20261016.png|'''Scenario 13: ATM, 500 km in 60 minutes.''' Local ascent preview and route comparison. The large TOTAL includes ideal powered gravity support. Labeled synthetic render, not a live flight.
File:Orbit-MFD-surface-sub-20261016.png|'''Scenario 14: SUB at the same PASS.''' Whole-route PLANE 3D view while still on the ground, with ballistic coast and numbered phase boundaries. Labeled synthetic render.
File:Orbit-MFD-surface-auto-20261016.png|'''Scenario 15: AUTO, 4000 km in 90 minutes.''' ORB fits the simplified model while ATM and SUB exceed thrust. This demonstrates the PASS constraint, not certified flight performance. Labeled synthetic render.

Select the intended surface waypoint on the usual navigation instrument. For an orbital departure, choose '''REENTRY'''. Planning is available while docked; undock before engaging DOR. The automated-entry alpha can fly an '''ENTRY READY''' profile from at least 100 km MSL to its atmospheric handoff. It requires current air data, main/reverse and translation thrust, and a clean configuration: gear, flaps and spoilers retracted, bay closed and no significant icing. A plan lacking those inputs remains '''PLAN ONLY'''. Below 100 km, a new entry shows '''ENTRY START BELOW 100km''' and no powered profile is searched; handoff settings remain available. An entry already executing continues on its committed guidance through this altitude. Earlier calibration clients label this mode REENTRY PLAN and cannot execute it.

|-
| REC || Administrator-only: record a manual test and the selected reference plan without engaging DOR. See below.

'''PEAK REV''' and '''RCS''' show the largest predicted fractions of available reverse-main and translation-RCS thrust anywhere in the entry. These are peaks, not constant throttle commands, and their peaks need not occur together. DOR uses the thrust needed to follow the selected profile rather than commanding 100% throughout. Translation RCS supplies vertical and sideways force that the modeled wings and mains do not provide, including descent shaping and weight support as orbital support diminishes. This profile is not an aerodynamic-only or minimum-RCS entry. The entry model uses current loaded mass, fuel consumption, main-engine condition, separate forward/reverse and up/down/side limits, engine response, Vieneo gravity/rotation/density, and the client's clean wing/tail/body and Mach-dependent aerodynamic model. It estimates AFT from the client's heat-transfer model. '''MAX q''' is the modeled effective aerodynamic pressure in kPa, including the client's Mach augmentation; it is distinct from ambient-density dynamic pressure. Cockpit Q is in lb/ft². '''LOAD''' is estimated non-gravitational acceleration in standard Earth g units.

The alpha's preview reports peak IAS as a percentage of Vne and peak predicted AFT. It requires at most '''95% of Vne''', '''200°C predicted AFT''' and '''95% of each available thrust axis''', plus its engine-response and attitude-rate checks. These are controller settings for validation, not newly established vehicle limits. AFT forecasting uses Vieneo's model and the current measured temperature/wind; it does not forecast changing weather, clouds or turbulence along the route. '''ALPHA / NO TERRAIN CHECK''' remains a limitation: neither the entry nor the ILS descent has a terrain or obstacle database, weather avoidance, flare or touchdown controller. Keep [[Atmospheric_Reentry|entry procedures]], AFT, IAS/Vne and flight path in view.

These checks use the client's Vieneo atmosphere and vehicle models. They do not certify a real aircraft, forecast terrain/clouds/aerosols, guarantee control after catastrophic damage, or automate landing. The nominal 20° descent belongs to the later atmospheric approach; it is not an instruction to force a 20° flight path at orbital-entry speed.

=== Automated entry alpha ===
# Start with a clean ship in orbit and select the surface destination. Use AUTO, H ALT 30 km and H TAS 0.5 km/s for the initial test.

# Undock if necessary, then engage DOR. AUTO selects a route; it does not engage DOR by itself. For administrators, an accepted entry starts a CSV capture automatically, so REC is not required for this test. Other accounts fly the same entry without diagnostic recording.

# To resume normal flight, cancel the entry TAS hold with the DOR control or by moving a physical throttle lever. The lateral and vertical guidance modes remain until changed or disconnected. Disconnecting the aircraft autopilot also ends the TAS hold. In the arrival/FPA alpha, TAS hold continues with HDG, NAV or LOC and PIT, VS, ALTm, ALTa, FPA or G/S. Selecting SpeedPitch, Roll, an off mode or TVM ends it. Ordinary gear/flap/spoiler changes after handoff retain TAS hold with updated drag compensation; icing, an open bay, unavailable/stale air data or lost authority still cancel it. Change H TAS on the DOR page to adjust the held speed. Outside automatic runway descent, manage speed for ATC routing, descent and approach: a fixed TAS can produce increasing IAS as you descend. During automatic runway descent, changing the target or a flight-guidance mode/target cancels the continuation, except that ILS LOC/G/S arming and LOC capture preserve managed vertical descent; the pilot’s selected mode remains in force. Cancelling TAS hold also stops automatic descent updates, so check the FMA and take over the remaining flight path.

For administrators, automatic recording continues through the handoff holds until they are cancelled. Retain both matching CSV files for review of the actual response, predicted heat/IAS, force commands, available thrust and handoff modes. Start testing with a comfortable preview, then shorten the requested time on subsequent flights; the alpha is not a certified fastest possible entry.

'''Final geometry:''' At least '''10 km''' is reserved for 3° final. ILS uses a unique loaded inbound outer marker when it is farther out; a nearer marker does not shorten that minimum. Otherwise the initial final distance is 10 km. The ILS join is '''15 m below the client's nominal beam''', within its descending-capture tolerance. The receiver uses MSL height difference and slant DME. VISUAL uses a 3° ray above the runway tangent, corrected for Vieneo's curvature. The displayed final altitude includes runway elevation and is '''MSL''', not terrain clearance.

'''Speed and thrust:''' The managed descent retains higher speed until denser air, predicted AFT or the braking distance to final calls for slowing. Its final IAS objective is the greater of Vref and 1.3 times current stall speed. The forecast uses the client's Vieneo atmosphere and Mach-dependent drag, with a 90% Vne planning target and 195°C thermal target below the entry's 95% Vne/200°C limits. These are controller margins, not newly certified vehicle limits. Pitch can shallow to preserve speed margin. Engine response and reverse-bucket travel are allowed for before final speed capture.

=== Recording a manual entry test ===
These recording controls require an administrator account.
# Select the target, route, handoff time, altitude and TAS; wait for an inspectable proposed path.
# Select REC and press Shift + Left/Right once to turn recording on. With the proposed path available, the row reads REC ON (REF). This does not engage DOR or command the ship.
# Fly the test manually or with appropriate existing Autoflyte modes. Changing VIEW or leaving the MFD page does not stop recording. The CSV reference stays fixed at recording start even while the live preview updates.
# Turn REC off to finish. Changing planning controls, changing target, resetting/changing the vehicle, or engaging an executable DOR plan also ends the manual capture. A new test requires REC on again.
# Return both matching files from the '''OrbitLogs''' directory beside the running executable: '''DOR-N.csv''' and '''DOR-N-plan.csv'''. The first contains actual flight data and timed comparison values; the second contains the frozen reference trajectory.

Four reusable file slots bound retention; older captures can be replaced by subsequent starts. A slot stops at 128 MiB rather than discarding its beginning. REC FILE ERROR or REC FILE FULL means capture has stopped. Current clients can start REC ON (FLIGHT) without a reference; older entry-calibration clients instead display REC WAIT FOR PLAN. Copy the pair you want to keep before beginning more tests. No automatic upload occurs.

New captures separately integrate main-engine, translational-RCS, attitude-RCS and idle fuel consumption, and record the available orbital MECO estimate. The tank-based ALL USED remains the measure of fuel actually lost; integrated component totals can differ slightly because of fuel-tank rounding.

The CSV includes time, target, mass/fuel, position/velocity, engine and RCS outputs, air-relative velocity, IAS, Mach, dynamic pressure, measured AFT and reference errors. The automated-entry alpha also records the predicted AFT/IAS reference, the live protection forecast, controller limits, force requests and handoff holds. Burn-and-coast profiles also record the intermediate coast start/end times and endpoint states. Earlier calibration captures contain measured AFT but no predicted temperature reference. An expired HANDOFF or end of recording does not prove that the entry was completed successfully.

| DOR: TIMING INTERRUPTED || A simulation frame took more than one second during ascent or an orbital maneuver. DOR disconnects; check the current flight state before re-engaging. An already executing reentry instead retains its plan and waits for fresh air data when needed. This message does not identify the cause of the client stall.

| ASCENT PROFILE REQUIRED || The selected vacuum orbital objective has no powered launch solution. Choose [[#Ground-to-rendezvous mission|MODE RENDEZVOUS]] for a continuous launch to an orbital target, or [[#Automated ascent alpha|MODE PARKING ORBIT]] for a standalone parking-orbit climb. Older clients require a manual ascent.

| PLAN ONLY / ATM HANDOFF || The displayed candidate is preview-only; DOR cannot execute it. Ground-departure SURFACE PLAN remains preview-only. REENTRY needs a qualifying ENTRY READY profile in the automated-entry alpha.

| NO TERRAIN / HEAT CHECK || SURFACE PLAN and older calibration previews omit these checks. Automated-entry REENTRY predicts heat but still displays ALPHA / NO TERRAIN CHECK.

| MODEL FIT / HEAT UNCHECKED || Older calibration-client preview; it does not support automated entry.

| REC FILE ERROR / REC FILE FULL || Capture stopped because of a file error or size cap. See [[#Recording a manual entry test|recording instructions]].
|-
| ENTRY FIRST / NO ROUTE AT THIS PASS || Direct ATM is outside its initial departure-height range, or no candidate was available at this deadline. Change ROUTE/PASS or use separate entry procedures.

[[Category:Getting Started]]