Your longest recorded sector is 117 NM
A useful anchor for understanding the upper end of the missions represented in this history.
One place for the retrospective side of RFoV: your aviation story, airports, explored territory, flying patterns and the relationships that emerged from your flights.
A cross-section of how this pilot actually flies: mission length, change over time, aircraft utilisation, network structure and discovery. Aircraft context uses canonical Fleet / Knowledge Pack characteristics where RFoV has them.
Insights explain recorded behaviour. They do not change Director FIT, flight ownership, Personal Story Arcs or aircraft data.
These are evidence-backed observations selected because they help explain this history, not because they assign a score.
A useful anchor for understanding the upper end of the missions represented in this history.
Both lenses are anchored to the latest completed flight in this history, so dormant periods do not distort the comparison.
Bar height is completed sectors. Gold at the base marks months containing first recorded arrivals.
1 of 1 sectors carry usable distance evidence.
Actual completed sectors are crossed with canonical aircraft characteristics. A gold Developer badge means the row has Knowledge Pack-backed characteristic evidence; otherwise RFoV uses the canonical Fleet planning layer.
Unique recorded connections reveal the airports holding different parts of your personal network together.
0 directed routes have been flown more than once · 0 airport pairs have traffic in both directions.
This is a chronology-aware measure of airports first appearing as arrivals in the canonical history, not a claim about real-world pilot experience.
Selective observations from your recorded history — not achievements to grind.
EGTF introduced your first recorded Short-field destination.
EGNE → EGTF starts the RFoV aviation story.
Compact SimConnect summaries from compatible PC Flight Logger flights. RFoV stores the evidence, not second-by-second telemetry.
Each story is refreshed from this pilot’s recorded completed-flight evidence. Where an aircraft image exists in the Hangar, RFoV uses it as the visual identity for the story.
RFoV curates the strongest longer stories it can support from this pilot’s completed history. Aircraft-led stories use the Hangar image where one is available; other arcs use an RFoV story motif.
Coordinate-resolved airports, aircraft positions, connections, frontiers, Journey intent and World Threads share one factual map. “Mapped airports” can be lower than the total recorded-airport count because some historical records do not have coordinates.
Threads are patterns RFoV notices in completed flights. You do not create, pause or complete them; they simply become more or less visible as your flying changes.
RFoV scans both current and earlier flight-history windows. Earlier Threads are still derived evidence, not permanent objectives. “Continue” only asks Flight Desk to look for a suitable next sector that fits the observed pattern.
0.2% of the current exploration grid · 1 frontier cells.
1 sectors · 1 destinations · 0 aircraft types.
These roles emerge from how you actually use airports rather than being configured manually.
10° cells are a lightweight exploration index, not an equal-area measure of Earth.
Descriptive, not a score or judgement.
Based only on airport/navdata evidence RFoV can support.
1 distinct recent destinations.
1 distinct recent destinations.
1 distinct recent destinations.
These analytical views still inform Flight Desk quietly, but they now live here rather than competing with flight choice.