NIL denotes no braking action. In braking action terminology, these terms describe how well a runway surface will allow an aircraft to decelerate. NIL means there is effectively zero usable friction; braking provides no useful deceleration, and stopping the aircraft becomes highly uncertain and much longer than normal. Pilots may have to rely heavily on thrust reversers and other procedures, and operations may be restricted or require a longer runway. Other terms indicate that some braking action remains (good, fair, poor), so nil is the only term meaning none at all. Some other words like zero or bad aren’t standard braking action terms in this context.

The entry for MTN461 identifies the Saab 340 as the aircraft type, encoded as SF34/A. In this data format, SF34 denotes the Saab 340, a twin-turboprop regional airliner, and the trailing A is a variant or equipment code. This makes SF34/A the correct match for MTN461’s entry because it directly reflects the type described in the record. The other options specify different aircraft types (Cirrus Vision Jet, Cessna 172, Beechcraft Baron 58) each with their own codes, which would not align with MTN461’s entry.

The beacon’s job is to mark the airport and make it visible to pilots, especially when visibility or cloud ceilings are poor. During daylight hours it isn’t required to stay on all the time; it’s turned on in the day only when the weather falls below basic VFR minima, so pilots can still locate the field in marginal conditions. This is why the statement that the beacon is turned on between sunrise and sunset when the weather is below VFR minima is the true one: it matches the rule that the beacon is active in daylight under marginal weather, and is always on at night. The other ideas—being on only when requested, or never used if visibility is good, or always on from sunrise to sunset—don’t reflect how beacons are used to aid visibility and airport identification under varying weather.

The balance is preserved when you end the edit in Overlay mode using the End switch. In Overlay mode, edits are layered on top of existing content rather than replacing it, so finishing with the End switch aligns the boundary of the overlay without disturbing the underlying material. This keeps the overall arrangement stable, whereas other mode-switch combinations tend to reflow or shift content at the end of the edit, breaking the balance.

The main idea here is using the correct FP string structure and field order for UAL114. A valid FP string should start with the FP header, include the flight number and aircraft type, then specify the speed, followed by the departure fix or initial waypoint, the cruising altitude block, and then the route with its waypoints ending at the destination with the appropriate airway tag. The best example follows that exact sequence: FP UAL114 DC10/A 440 ELN P1800 330 ELN..EPH.V2.GEG. It starts with FP and the correct flight information, places the speed before the route, shows the departure fix ELN, then the altitude block P1800 and the next figure, then the route ELN..EPH.V2.GEG which uses V2 to connect toward the destination GEG. The other strings diverge from this established order or use an incorrect final segment, so they don’t match the expected FP formatting for this scenario.