RF
RFoVRetro Faction of Voltrigones · Aviation Operations Network
FenixA320 CFM WFRJCJ
LINK ESTABLISHED// FLEET CONTROL2026-09-26 Z04:57 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 58P Professional N513LW · N513LWBriefed6D9 → 34UFlight 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

MH60 Tango

Current recorded location: 0WA7

Sectors32
Distance350 NM
Airports30
Registrations seen5
Configurations seen1
6042BOP-356356UnknownN123AZ
Aircraft Characteristics

Developer aircraft data

Miltech Simulations MH60 Tango — Structured Rotorcraft Knowledge v1.0.0 · Exact match
Developer data
Aircraft classLong-range SAR / medevac rotorcraft
Access capabilityRotorcraft / vertical-access sites
PowerplantTurboshaft × 2
Source: Miltech Simulations / Blackbird Simulations · Miltech Simulations Documentation Hub — MH60 · Quick Start p.35 — MH60T long-range SAR, medevac and maritime patrol. 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 + saved planning values · Miltech Simulations MH60 Tango — Structured Rotorcraft Knowledge v1.0.0
Long-range SAR / medevac rotorcraft125 kt5,000 ft cruise21–245 NMVFR / IFR depending on fit
Cruise / plan speed125 kt
Normal cruise1,000–5,000 ft
Max planning altitude10,000 ft
Comfortable sector21–245 NM
Practical range395 NM
Runway assumption0 ft
Surface characterMixed / flexible
Access capabilityRotorcraft / vertical-access sites
RoleLong-range SAR / medevac rotorcraft
Your actual use: median sector 14 NM · longest 76 NM · highest recorded flight altitude 10,217 ft. You tend to use this aircraft for shorter flights than its current planning envelope.
SimBrief handoff profile

MH60 Tango

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

Not identified · 6042

Detected suggestion: none — set the SimBrief type manually. A SimBrief custom airframe Internal ID can also be stored here.
Aircraft Story

MH60 Tango

RFoV has recorded 32 sectors in this aircraft across 30 airports. Its story currently continues from 0WA7. Charter work has become a visible part of this aircraft story.

First recorded sectorEGCN → 5327N00151W2026-02-28 01:05:47
Longest recorded sectorKBCE → UT9176 NM
Most familiar regionAlaska, United States9 recorded arrivals
Latest recorded sector70WA → 0WA7Currently recorded at 0WA7
Charter chapter1 completed assignmentWildreach Air Services is the most frequent operator · 1 passengers · 36 kg cargo
Story facts are refreshed from completed RFoV history. They do not assert a real-world aircraft state.
Aircraft Story Continuity

Possible next chapters

RFoV uses this airframe’s recorded history plus the current suitable opportunity set to suggest where its story could go next.

Keep this airframe movingMH60 Tango is recorded at 0WA7. Continue its next chapter from there.
Add a new airportMT54 does not yet appear in this aircraft’s recorded airport history.
Open a new regionHaiti would extend this aircraft’s recorded geographic story.
Extend its range frontier117 NM would exceed this aircraft’s current longest recorded sector of 76 NM.
Continue this aircraft →
Continuation cues are derived from recorded simulator history and currently suitable RFoV opportunities; they do not assert real-world aircraft state.
Fleet career

Milestones

Airframe-level progress, independent of individual tail numbers.

First sector32 / 1
Regular32 / 10
Veteran32 / 25
Explorer30 / 10
1,000 NM349 / 1,000
Recent movements

Where this airframe has flown

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

25 mapped · 7 without usable coordinates
Selected / latest sectorOther displayed sectors
Airframe logbook

Recorded sectors

DateRouteSourceRegistrationDistance
September 23, 202670WA → 0WA7Flight Logger604259.4 NMMapOpen →
August 18, 2026KSAC → KSCKHistorical LogBOP-356—MapOpen →
August 18, 2026KSAC → KSMFHistorical LogBOP-356—MapOpen →
August 17, 2026KNTU → KO61Historical LogBOP-356—Open →
August 17, 2026KNTU → KO61Historical LogBOP-356—Open →
August 17, 2026MDCS → KNTUHistorical LogBOP-356—Open →
August 17, 2026MDCS → KEYWHistorical LogBOP-356—Open →
August 17, 2026MDPP → MDPPHistorical LogBOP-356—MapOpen →
August 17, 2026TUPW → MDPPHistorical LogBOP-356—MapOpen →
March 25, 2026XPLO → EGPEHistorical Log356—Open →
March 25, 2026EG6YA → 5710N00521WHistorical Log35629.8 NMMapOpen →
March 25, 2026XPLO → XPLOHistorical Log356—Open →
March 7, 2026KBCE → UT91Historical LogUnknown76.0 NMOpen →
March 7, 2026PAKD → 4K5Historical LogUnknown8.0 NMMapOpen →
March 5, 2026PAKD → PAKDHistorical LogUnknown—MapOpen →
March 1, 2026PADQ → PADQHistorical LogN123AZ—MapOpen →
February 28, 20265731N15248W → PAKDHistorical LogN123AZ22.1 NMMapOpen →
February 28, 20265730N15236W → 5731N15248WHistorical LogN123AZ11.9 NMMapOpen →
February 28, 20265733N15232W → 5730N15236WHistorical LogN123AZ5.3 NMMapOpen →
February 28, 20265735N15249W → 5733N15232WHistorical LogN123AZ38.4 NMMapOpen →
February 28, 20265735N15249W → 5735N15249WHistorical LogN123AZ0.0 NMMapOpen →
February 28, 2026PAKD → 5735N15249WHistorical LogN123AZ19.9 NMMapOpen →
February 28, 2026PAKD → PAKDHistorical LogN123AZ0.0 NMMapOpen →
February 28, 2026PAKD → PADQHistorical LogN123AZ—MapOpen →
February 28, 20265739N15220W → PAKDHistorical LogN123AZ0.1 NMMapOpen →
February 28, 2026PAKD → 5739N15220WHistorical LogN123AZ11.4 NMMapOpen →
February 28, 2026PAKD → PADQHistorical LogN123AZ—MapOpen →
February 28, 2026PAKD → PAKDHistorical LogUnknown—MapOpen →
February 28, 2026EGHH → 5756N15236WHistorical LogN123AZ16.9 NMMapOpen →
February 28, 2026PADQ → PADQHistorical LogN123AZ—MapOpen →
February 28, 20265327N00150W → 5327N00150WHistorical LogN123AZ0.3 NMMapOpen →
February 28, 2026EGCN → 5327N00151WHistorical LogN123AZ50.1 NMMapOpen →
Procedures & checklists

MH60 Tango

Miltech Simulations MH60 Tango — Structured Rotorcraft Knowledge · Structured · Exact aircraft 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 simulator controls needed by the developer aircraft are mapped before beginning a cold start.

  1. Verify cyclic pitch/roll, collective and anti-torque pedal axes respond correctly.
  2. Ensure the helicopter-throttle axis is not being used; the simulated governor manages rotor/engine speed.
  3. Confirm the rotor-brake command is mapped and behaves as expected.
  4. Review any mission-system keybinds needed for the planned flight.
Miltech Simulations Documentation Hub — MH60 · Recommended Hardware Configuration / Keybinds · pp.18-28

Set the aircraft for a powered cold-start sequence and remove external items that would block operation.

  1. Secure the aircraft on the ground with chocks/parking brake as appropriate and lock the tail wheel.
  2. Confirm engine/APU fire controls are in their normal pre-start positions and perform the simulated fire-detection test.
  3. Remove exhaust/pitot covers and other configured ground items before start.
  4. Load mission equipment or flight-plan data required for the sortie before engine start.
Miltech Simulations Documentation Hub — MH60 · Normal Procedures S/R/T · Before Start · pp.43-45
Startup · 2

Bring the electrical/APU and flight-computer systems online before engine start.

  1. Switch battery power on, configure lighting as required and set the ECS/air-source system for APU operation.
  2. Enable fuel boost/prime functions required for APU start, start the APU and bring its generator online.
  3. Power the primary/backup computers, mission/flight displays and both EGI systems, allowing alignment to progress.
  4. Set/uncage barometric and standby instruments, review the systems page, acknowledge cautions and verify fuel indications.
  5. Set radio/navigation/transponder and radar-altimeter references for the planned flight.
Miltech Simulations Documentation Hub — MH60 · Normal Procedures S/R/T · Before Start · pp.44-45

Start engine 1 and engine 2 in sequence, then transition the rotorcraft from APU-supported start to normal engine-powered operation.

  1. Confirm the area and doors are secure; verify SAS 1, SAS 2, TRIM and stabilator automatic control are enabled.
  2. Set ignition/fuel controls for start and start engine 1 only after the indicated turbine temperature is suitably low.
  3. Move engine 1 PCL to idle and confirm the displayed engine values are within the simulated limits, then repeat for engine 2.
  4. Check oil pressure and engine-speed agreement, release the rotor brake and move both PCLs to the flight position.
  5. Verify rotor/engine percentage and torque balance, select the normal fuel-feed positions and switch both main generators on.
  6. Transfer the ECS to engine supply, remove the APU generator and shut the APU down; configure de-ice as conditions require.
Miltech Simulations Documentation Hub — MH60 · Normal Procedures S/R/T · Engine Start · p.46
Taxi / Run-up · 1

Remove ground restraints and establish the ground-handling configuration before moving.

  1. Remove chocks, set exterior lighting as required and release the parking brake.
  2. Release/unlock the tail wheel for manoeuvring and confirm steering response.
  3. Keep the taxi area clear and monitor flight/engine indications during movement.
Miltech Simulations Documentation Hub — MH60 · Normal Procedures S/R/T · Before Taxi · p.47
Takeoff · 1

Set flight-control augmentation, environmental/ice protection and departure configuration before lift-off.

  1. Set lights and anti-ice/pitot/de-ice equipment for the conditions.
  2. Confirm SAS 1, SAS 2 and TRIM remain on and stabilator automatic control is enabled.
  3. Review instruments and warning/caution/advisory indications and set the transponder.
  4. Lock the tail wheel for departure and establish the intended takeoff collective/configuration.
Miltech Simulations Documentation Hub — MH60 · Normal Procedures S/R/T · Before Takeoff · p.47
Climb · 1

Maintain the shared MH60 systems configuration and monitor aircraft state as the departure transitions into climb.

  1. Use lighting and ice-protection systems as required by conditions.
  2. Select AFCS/autopilot assistance only as appropriate to the flight segment.
  3. Monitor instruments and warning/caution/advisory indications.
  4. Track fuel consumption during the climb.
Miltech Simulations Documentation Hub — MH60 · Normal Procedures S/R/T · Climb and Cruise · p.47
Cruise · 1

Continue system, fuel and AFCS monitoring while established en route.

  1. Set lighting and anti-ice/de-ice systems as required.
  2. Use AFCS/autopilot modes as appropriate and continue monitoring the aircraft rather than treating automation as autonomous navigation.
  3. Review instruments/WCA indications periodically.
  4. Monitor fuel consumption against the planned sortie.
Miltech Simulations Documentation Hub — MH60 · Normal Procedures S/R/T · Climb and Cruise · p.47; AFCS/SAS overview · p.39
Approach · 1

Reconfigure the aircraft for the intended landing area and verify the landing site is clear.

  1. Set lights as required and review instruments and warning/caution/advisory indications.
  2. Check fuel consumption/state before the terminal manoeuvre.
  3. Lock the tail wheel as required for the landing configuration.
  4. Confirm the intended landing area is clear before committing to the final landing manoeuvre.
Miltech Simulations Documentation Hub — MH60 · Normal Procedures S/R/T · Before Landing · p.48
Landing · 1

Maintain the chosen stabilisation/hover mode and land into the cleared area without treating RFoV as an aircraft-control system.

  1. Maintain the required cyclic/collective/pedal control or selected AFCS assistance through touchdown.
  2. Confirm the aircraft is stable on the surface before changing the ground-handling configuration.
Miltech Simulations Documentation Hub — MH60 · Quick System Overview / AFCS-SAS · pp.39, 159-166; Normal Procedures S/R/T · p.48
After Landing · 1

Transition from flight to ground operation and prepare the APU before engine shutdown.

  1. Neutralise flight controls as appropriate, use brakes as required and set the tail-wheel state for ground manoeuvring.
  2. Set lighting as required and switch flight ice-protection equipment off when no longer needed.
  3. Select ECS air source to APU, enable the required APU prime/boost functions and start the APU.
  4. Bring the APU generator online before proceeding to shutdown.
Miltech Simulations Documentation Hub — MH60 · Normal Procedures S/R/T · After Landing · p.48
Parking · 1

Stabilise the aircraft on the ground before engine shutdown and post-flight securing.

  1. Lock the tail wheel, set the transponder to standby and set the parking brake.
  2. Install chocks when appropriate before removing engine power.
  3. Confirm the aircraft is positioned safely for rotor-brake and shutdown actions.
Miltech Simulations Documentation Hub — MH60 · Normal Procedures S/R/T · Engine Shutoff/Aircraft Switchoff · p.49
Shutdown · 1

Use the shared S/R/T shutdown sequence to remove engine power, stop the rotor and de-energise the aircraft.

  1. Switch both main generators off and set engine ignition off.
  2. Allow both PCLs to remain at idle for the developer-specified cool-down period before moving engine/fuel controls off in sequence.
  3. Apply the rotor brake as required after engine shutdown and disable stabilator auto, SAS/TRIM and utility hydraulic systems.
  4. Configure blade/tail fold only when desired and when the simulated prerequisites are satisfied.
  5. Power down computers, EGI, mission/flight displays and lights.
  6. Remove APU generator/air source, shut down the APU/prime/boost systems and finally switch the battery off.
Miltech Simulations Documentation Hub — MH60 · Normal Procedures S/R/T · Engine Shutoff/Aircraft Switchoff · p.49; Tail/Rotor Fold · pp.51-53