Risk Page Reference

Related documents

• Page Reference
• Aircraft Type Reference
• Wind Reference

Table of Contents

• Introduction
  • What the app must supply
  • Setting items from the app
  • Scoring
  • Persistence
• Page state variables

Introduction

The Risk page (page ID risk, title "Risk") is a Flight Risk Assessment Tool (FRAT). It is defined in common/page/risk.js. The user answers a list of risk questions grouped into cards: General flight, Human factors, Departure Area, Enroute, and Destination Area. Each answered item contributes points. The page totals them, shows the total on a dial meter with a risk level, and displays a recommendation. The point values and the combined risks are described in the page's help topic.

The page is optional and aircraft-dependent. An aircraft app includes it by importing the file for its side effect and listing risk in its nav layout:

import './common/page/risk.js';

The C172, C182, PA28, Baron, Bonanza, Kodiak, and TBM apps use it. The Radar app doesn't.

What the app must supply

The page reads the following, so the app must define them:

• acData.risk, an object of per-aircraft thresholds: singleEngine (true for single-engine aircraft, which raises the water-crossing risk and enables the single-engine night over-water no-go), minRunway, maxWind, maxXwind, plus wideRunway, minFuel, areaImc, and areaLifr which the app's Aircraft page copies into display state variables.
• The Aircraft page output state variables that the page displays in its labels: ac_riskMaxWind_kt, ac_riskMaxXwind_kt, ac_riskMinRunway_ft, ac_riskWideRunway_ft, ac_riskMinFuel_min, ac_riskAreaImc_nm, and ac_riskAreaLifr_nm.
• The state variables of the Departure, Destination, and Enroute pages that the page copies from: dep_runwayLength_ft, dep_windSpeed_wkt, dep_windDir, dep_crosswind, dep_flightCategory, the same dest_ set, dest_areaImcRisk, dest_areaLifrRisk, and enrt_flightRules. The page also uses the Wind class and acType.hasOption('fiki') (known ice).

Setting items from the app

When any of those app state variables changes (and they are all valid), the page presets some risk inputs: a short departure or destination runway (shorter than minRunway), wind at or above maxWind, crosswind at or above maxXwind, the flight rules, the departure and destination flight categories (when known), and the destination area IMC and LIFR flags. The user can change them afterward, and a later change in the app overwrites them again. "Clear All" resets every risk input to its default.

Scoring

Each risk input state variable has a matching <id>Points output state variable. A checkbox contributes its value when checked. Selectors map each option to points. Some values depend on IFR (risk_flightRules) or on the FIKI option. A fixed value of 32 (riskMax) marks a no-go item. A set of combined risks (risk_singleEnginePoints, risk_imcNoApPoints, risk_imcCtlPoints, risk_imcCtlNightPoints, risk_imcCurrencyPoints, risk_noGsNightPoints, risk_destNightTerrainPoints, risk_nightLimitPoints) adds points for combinations of inputs, and risk_nightLimitPoints limits the total night points to 2. The "Combined Risks" card is shown only when any combined risk is non-zero. The IFR-only rows are shown only when risk_flightRules is IFR.

The total is clamped to 0 to 32 and classified:

The level is available as risk_level, the message as risk_msg, and the meter redraws when nav_darkMode changes.

Persistence

The risk inputs are input state variables with the default save mode, so they are saved with the app state.

Page state variables

All the state variables have the prefix risk_.