Pilot notes and personal constraints
The notes box at the bottom of the request form is free text, and it is the place to tell the analysis the things no dropdown can capture.
What belongs there
Personal minimums. Your limits, not the regulation's:
"No over-water legs. Keep me at least 20 NM clear of any convective SIGMET. No night landings at unfamiliar fields."
Route description, when waypoints cannot express it — cities, towns and landmarks. See Waypoints.
Context about the flight. A passenger who gets airsick, a hard arrival time, a first flight after a long layoff, a check ride in three days, an aeroplane you collected from maintenance this morning.
Equipment reality. "The autopilot altitude hold is inoperative." "No oxygen on board." "Portable ADS-B only."
What you already decided. "I will not continue past Rumford if the ceiling is below 4,500."
How the analysis uses it
Your constraints are treated as your limits and are checked against the flight as planned. If the forecast puts you inside a limit you set, the report says so directly and puts it among the critical factors, rather than telling you the flight is legal and leaving it there.
Positive context is used too: an instructor on board, a familiar airport, an aircraft you fly weekly — these appear among the positive factors.
What not to put there
- Anything you need the analysis to calculate from structured data — fuel, altitude, times and the aircraft all have their own fields, and the fields are what the calculations read.
- Personal information about other people. The report can be printed, emailed and stored.