JetVA Community

Jetva.co.uk Forum

Operations, support, flight discussion and community updates.

Jet Track Scoring Profiles

Read 4 times
Pages 1

 

Introducing Jet Track

Our new flight tracking and scoring system for JetVA.

Summary:
Jet Track is our new flight tracking system, currently being developed and tested for JetVA. It is designed to give us more accurate flight evidence, cleaner PIREP data and a more realistic scoring model than the older systems we have used previously.

What is Jet Track?

Jet Track is a new flight tracker being built specifically for JetVA. It records flight data from the simulator, builds the evidence used in the PIREP, and applies a server-side scoring system based on the aircraft being flown.

The aim is to move toward a more realistic and fair scoring model. Rather than treating every aircraft the same, Jet Track uses aircraft profiles. This allows an Airbus A320, Airbus A330 and Boeing 737-800 to be handled differently where they should be.

This system is still being developed and refined, so scoring may continue to change as more real flight data is tested and validated.

Why are we doing this?

Older tracking and scoring systems were useful, but they were limited. They could sometimes treat aircraft too generically, over-reward certain landings, or make it harder to tell the difference between a genuine issue and a harmless simulator data spike.

Jet Track is intended to give us cleaner flight logs, better scoring evidence, and a more consistent review process.

How the scoring works

Aircraft limits are aircraft/profile-specific values, such as flap speeds, gear speeds, maximum takeoff weight and maximum landing weight.

Operational discipline covers expected airline-style handling, such as taxi speed, landing lights and approach behaviour.

JetVA scoring policy controls points, penalties, bonuses, reviews and auto-accept behaviour.

Important:
The system is not designed to punish every tiny mistake. It is designed to separate normal flying, minor issues, review items and serious events more clearly.

First scoring alignment: Airbus fleet

The first major scoring alignment has now been completed for the Airbus profiles. This covers taxi speed, landing lights and landing-rate scoring.

This does not mean every Airbus has been made identical. Aircraft-specific limits remain separate. The alignment is about making common Airbus operating expectations consistent across the supported Airbus profiles.

Aircraft covered in this Airbus pass

A20N Airbus A320neo
A21N Airbus A321neo
A319 Airbus A319 Generic
A319FSL Airbus A319 FSLabs
A320 Airbus A320 Generic
A320FENIX Airbus A320 Fenix
A320FSL Airbus A320 FSLabs
A320JARD Airbus A320 JARDesign
A320UFF Airbus A320 Ultimate
A321 Airbus A321 Generic
A321FENIX Airbus A321 Fenix
A321FSL Airbus A321 FSLabs

The Airbus A330-200 has also been reviewed separately as a widebody. It is not scored exactly the same as the A320 family.

Taxi speed scoring

Airbus taxi rule:
Taxi speed above 35 kt
Penalty: -10 points
Delay: 5 seconds
Severity: Minor
Maximum: one hit per flight

This is an operational discipline rule, not an aircraft structural limit. A brief spike should not ruin a report, but sustained excessive taxi speed will be captured.

Landing-light scoring

Airbus landing-light rules:
Landing lights on above 10,000 ft: -5 points
Landing lights off below 10,000 ft: -5 points
Severity: Minor

This follows normal Airbus-style 10,000 ft transition logic. The penalty is small because simulator aircraft can expose light states differently. The aim is to encourage correct operating habits, not heavily punish a small switch issue.

Airbus narrowbody landing-rate scoring

This applies to the A319/A320/A321/A20N/A21N family and supported simulator variants.

0 to -75 fpm = Soft / floated = -5 = no review
-75 to -250 fpm = Good landing = +50 = no review
-250 to -360 fpm = Normal landing = +25 = no review
-360 to -500 fpm = Firm landing = 0 = review
-500 to -650 fpm = Hard landing = -50 = review
Below -650 fpm = Severe impact = -100 = review and auto-accept blocked

Jet Track is not chasing the lowest possible landing rate. A very low touchdown rate can also mean a float or long touchdown. The scoring is intended to reward a controlled and realistic landing, not just a soft number.

Airbus A330-200 landing-rate scoring

The A330-200 is handled separately and has wider landing-rate bands than the narrowbody profiles.

0 to -75 fpm = Soft / floated = -5 = no review
-75 to -250 fpm = Good landing = +50 = no review
-250 to -400 fpm = Normal landing = +25 = no review
-400 to -600 fpm = Firm landing = 0 = review
-600 to -750 fpm = Hard landing = -50 = review
Below -750 fpm = Severe impact = -100 = review and auto-accept blocked

What has not been changed yet?

Some items have deliberately not been bulk-changed yet:

Flap speed limits
Gear speed limits
Maximum takeoff weight
Maximum landing weight
Minimum landing fuel
Raw simulator flap-position mapping

These are aircraft-specific or add-on-specific. A Fenix Airbus, FSLabs Airbus and older generic aircraft may not expose every simulator value in exactly the same way, so these areas will be refined carefully profile by profile.

Will this make scoring harsher?

Not really. It should make scoring fairer.

The system now gives a clearer difference between a good controlled landing, a normal landing, a firm landing that needs review, a hard landing, and a severe impact that should not be auto-accepted.

What happens next?

This Airbus alignment pass is now complete for taxi speed, landing lights, Airbus narrowbody landing-rate scoring and separate A330-200 widebody landing-rate scoring.

Future Jet Track work will focus on Boeing / Jet2-style scoring profiles, especially the PMDG 737-800, plus flap-detent mapping, gear-speed limits, aircraft weights, fuel rules and approach-stability scoring.

Bottom line:
Jet Track is a new JetVA flight tracking and scoring system. This Airbus update is the first major scoring alignment pass. The aim is a cleaner, fairer and more realistic scoring model while keeping aircraft-specific limits separate where needed.

 


Many Thanks,

Mark.

Pages 1