RF
RFoVRetro Faction of Voltrigones · Aviation Operations Network
FenixA320 CFM WFRJCJ
LINK ESTABLISHED// FLEET CONTROL2026-09-26 Z02:19 ZOPS: NORMAL
PILOT CONTEXT
Fleet Control

Fleet & Hangar

Your persistent aircraft, configurations, positions and operational capabilities — ready to support the next flight.

Pilot stateFenixA320 CFM WFRFoV Network
Personal Living World
Viewing boppaViewing context only · Logger ownership still follows the Pilot Key
✈Black Square Baron 58TC Professional N7733K · N7733KBriefedGMMH → GQNGFlight Desk →
Personal Fleet

Hangar

Your aircraft are grouped by airframe rather than tail number. Detailed Flight Logger records remain rich; historical records join the fleet wherever an aircraft name was actually recorded.

Manage declared aircraft
0 declared · console / CoxBox / manual pilots
The key authorises only the Add or Remove action you submit. RFoV does not save it in the browser.
Declared aircraft are availability evidence only. They remain at zero sectors and zero distance until factual flight evidence exists.
← All airframesContinue this aircraft →View Full Career Map →
Airframe record

FlySimWare C414AW Chancellor

Current recorded location: KGNV

Sectors26
Distance1,484 NM
Airports29
Registrations seen5
Configurations seen2
Flysimware C414AW N641CP GNS530Flysimware C414AW N641CP PMS50 GTN750
N641CPBOP-356N9532N9532NN123AZ
Aircraft Characteristics

Developer aircraft data

FlySimWare C414AW Chancellor RAM IV — Developer Characteristics v1.0.0 · Pattern match
Developer data
Aircraft classPressurised executive piston twin
PowerplantPiston × 2
Maximum cruise240 kt
Normal cruise230 kt
Service ceiling30,000 ft
Normal range1,046 NM
Maximum range1,140 NM
MTOW3,223 kg
Max landing weight3,062 kg
Fuel capacity561 kg
Passenger seats7
Maximum payload709 kg
Useful load913 kg
Published full-fuel payload432 kg
Published takeoff distance2,185 ft
Published landing distance4,000 ft
Source: FlySimWare · C414AW Chancellor - RAM IV Conversion Manual · Technical Specifications p.5 · Cabin Seats p.38. RFoV uses only characteristics explicitly carried by the Knowledge Pack; missing planning dimensions continue to use saved values or RFoV heuristics.
Fleet Planning Intelligence

Planning envelope

Source: Developer data + RFoV planning heuristics · FlySimWare C414AW Chancellor RAM IV — Developer Characteristics v1.0.0
Pressurised executive piston twin230 ktFL200 cruise80–750 NMIFR capable
Cruise / plan speed230 kt
Normal cruise8,000–20,000 ft
Max planning altitude28,000 ft
Comfortable sector80–750 NM
Practical range1,046 NM
Runway assumption4,000 ft
Surface characterHard-surface focused
Access capabilityRunway / conventional airport access
RolePressurised executive piston twin
Your actual use: median sector 144 NM · longest 295 NM · highest recorded flight altitude 4,862 ft.
SimBrief handoff profile

Flysimware C414AW N641CP GNS530

RFoV uses this identity only when handing a selected IFR flight to SimBrief. It does not generate the IFR route itself.

C414 · N641CP

Detected suggestion: C414. A SimBrief custom airframe Internal ID can also be stored here.
Fleet career

Milestones

Airframe-level progress, independent of individual tail numbers.

First sector26 / 1
Regular26 / 10
Veteran26 / 25
Explorer29 / 10
1,000 NM1,484 / 1,000
Recent movements

Where this airframe has flown

Start with the latest sector, or widen the map to recent movements.

21 mapped · 5 without usable coordinates
Selected / latest sectorOther displayed sectors
Airframe logbook

Recorded sectors

DateRouteSourceRegistrationDistance
September 20, 202628J → KGNVFlight LoggerN641CP37.9 NMMapOpen →
September 20, 2026KNIP → 28JFlight LoggerN641CP47.9 NMMapOpen →
August 29, 2026SAWH → SCCIFlight LoggerN641CP148.6 NMMapOpen →
June 2, 2026KLHW → KNIPHistorical LogBOP-356—MapOpen →
April 27, 2026KMCI → KLHWHistorical LogN9532N—MapOpen →
April 27, 2026KPDK → KLZUHistorical LogN9532N—MapOpen →
April 27, 2026KPDK → KLHWHistorical LogN9532N182.0 NMMapOpen →
April 8, 2026KZME → KPDKHistorical LogN9532N—Open →
April 8, 2026KSRB → KPDKHistorical LogN9532N144.0 NMMapOpen →
March 29, 2026KZDC → KSRBHistorical Log9532N—Open →
March 29, 2026KHSP → KSRBHistorical LogN9532N295.0 NMMapOpen →
March 29, 2026KADW → KHSPHistorical LogN9532N—MapOpen →
March 29, 2026KADW → KADWHistorical LogBOP-356—MapOpen →
March 28, 2026W00 → KHSPHistorical LogN9532N155.0 NMMapOpen →
February 20, 2026KBLM → KAPGHistorical LogN123AZ—MapOpen →
February 20, 2026KBLM → W00Historical LogN9532N143.0 NMMapOpen →
February 19, 2026KTTN → KZNYHistorical LogN123AZ—Open →
February 15, 2026KBID → KGONHistorical LogN123AZ—MapOpen →
February 15, 2026KBID → KEWRHistorical LogN123AZ—MapOpen →
February 14, 2026K1B2 → KBIDHistorical LogN123AZ—Open →
February 14, 2026KNCA → K1B2Historical LogN123AZ—Open →
January 23, 2026KPLB → KOQUHistorical LogN9532N207.0 NMMapOpen →
January 22, 2026CYJN → KPLBHistorical LogN9532N37.0 NMMapOpen →
January 22, 2026CSC3 → CYJNHistorical LogN9532N49.0 NMMapOpen →
January 21, 2026CYSC → CSC3Historical LogN9532N38.0 NMMapOpen →
January 19, 2026CYSC → CYSCHistorical LogN9532N—MapOpen →
Procedures & checklists

Flysimware C414AW N641CP GNS530

Generic RFoV simulator checklist · Generic · Fallback_characteristics_only match

Open in Flight Desk

Reference view of the developer-sourced Knowledge Pack. It shows the whole library without contextual filtering. Check marks are local to this browser and do not change the live Flight Companion state.

Preparation · 2

Confirm the intended aircraft, route, fuel/load and simulator configuration are ready for this flight.

  1. Confirm aircraft/route/load setup.
  2. Review departure and arrival context.
  3. Verify the aircraft is in a safe pre-start state.
RFoV Generic Simulator Checklist Scaffold · Preparation

Review departure, destination, weather, temperature, time-of-day and any unusual RFoV context before starting.

  1. Confirm aircraft/route/load setup.
  2. Review departure and arrival context.
  3. Verify the aircraft is in a safe pre-start state.
RFoV Situational Context · Preparation
Startup · 2

Bring the aircraft from its initial state to a stable running/ready state using the add-on’s normal controls and indications.

  1. Establish electrical/fuel/engine start configuration.
  2. Start engine(s) using the add-on normal procedure.
  3. Confirm stable engine/electrical indications.
RFoV Generic Simulator Checklist Scaffold · Startup

Confirm the engine(s), electrical system and essential instruments show a normal simulator state before movement.

  1. Establish electrical/fuel/engine start configuration.
  2. Start engine(s) using the add-on normal procedure.
  3. Confirm stable engine/electrical indications.
RFoV Generic Simulator Checklist Scaffold · Startup
Taxi / Run-up · 2

Before committing to taxi, confirm braking/steering response and that primary flight controls move as expected.

  1. Confirm brakes/steering.
  2. Check primary flight controls and instruments.
  3. Complete departure/navigation setup before runway entry.
RFoV Generic Simulator Checklist Scaffold · Taxi

Confirm navigation/avionics, departure runway, initial plan and takeoff configuration are ready before entering the runway.

  1. Confirm brakes/steering.
  2. Check primary flight controls and instruments.
  3. Complete departure/navigation setup before runway entry.
RFoV Generic Simulator Checklist Scaffold · Taxi
Takeoff · 2

Confirm runway, controls, configuration and engine indications are appropriate for the planned simulator departure.

  1. Confirm runway and takeoff configuration.
  2. Re-check engine/system indications.
  3. Confirm any unusual weather/runway context before applying takeoff power.
RFoV Generic Simulator Checklist Scaffold · Takeoff

Re-check any weather, temperature, visibility or runway context RFoV has highlighted for this departure.

  1. Confirm runway and takeoff configuration.
  2. Re-check engine/system indications.
  3. Confirm any unusual weather/runway context before applying takeoff power.
RFoV Situational Context · Takeoff
Climb · 1

Transition from takeoff configuration to the normal climb state and confirm engine/instrument indications remain normal.

  1. Transition from takeoff to climb configuration.
  2. Set the planned climb power/speed.
  3. Monitor engine and flight instruments.
RFoV Generic Simulator Checklist Scaffold · Climb
Cruise · 1

Set an appropriate cruise configuration and periodically monitor engine, fuel and flight instruments.

  1. Establish cruise power/configuration.
  2. Check fuel/engine/instruments periodically.
RFoV Generic Simulator Checklist Scaffold · Cruise
Descent · 1

Review arrival weather/runway context, configure navigation as needed and establish a suitable descent state.

  1. Review arrival weather/runway.
  2. Set descent/navigation configuration.
  3. Brief the approach/landing plan.
RFoV Generic Simulator Checklist Scaffold · Descent
Approach · 1

Confirm the intended runway/approach, landing configuration plan and relevant aircraft systems before final approach.

  1. Confirm runway/approach.
  2. Set landing configuration progressively.
  3. Verify final approach setup.
RFoV Generic Simulator Checklist Scaffold · Approach
Landing · 1

Verify the aircraft is in the intended landing configuration and the runway/landing plan remains appropriate.

  1. Confirm final landing configuration.
  2. Continue only with a stable simulator approach.
RFoV Generic Simulator Checklist Scaffold · Landing
After Landing · 1

After clearing the runway, return the aircraft to a safe taxi configuration and adjust lights/systems as appropriate.

  1. Clear the runway.
  2. Return to taxi configuration.
  3. Reconfigure lights/systems as appropriate.
RFoV Generic Simulator Checklist Scaffold · After Landing
Parking · 1

Set the parking brake and place avionics, electrical and other aircraft systems into the intended parked state.

  1. Set parking brake.
  2. Secure/stow aircraft systems for shutdown.
RFoV Generic Simulator Checklist Scaffold · Parking
Shutdown · 1

Shut down the engine(s) and remaining aircraft systems using the add-on’s normal shutdown sequence, then secure the aircraft.

  1. Stop engine(s) using the aircraft normal sequence.
  2. Switch avionics/electrical systems off as appropriate.
  3. Leave the aircraft in a secured state.
RFoV Generic Simulator Checklist Scaffold · Shutdown