Paste each position into one box in degrees and decimal minutes, for example N63 59.1 W022 36.3. Use N/S for latitude and E/W for longitude. A space or comma between latitude and longitude is accepted.
02 · Aircraft and wind
Default TAS is 436 kt, the planning figure you supplied for the 787-9 at FL100, one engine inoperative. It is an adjustable assumption, not a verified company performance value. Mach is an optional reference only; it is not converted to TAS. Wind direction is entered as degrees TRUE, FROM.
03 · Equal time point
ETP position · Degrees and decimal minutes
—
—
Time either way—
Route distance—
Distance from departure—
Distance to destination—
Outbound GS at ETP—
Return GS at ETP—
DepartureETPDestination
Operational limitation: This is an independent planning aid, not an approved EFB, flight-planning system or operational source. It assumes constant TAS and a spatially uniform wind, no route changes, and a return along the same great-circle track. Verify independently against approved company procedures, aircraft performance data and current operational weather before any use. Do not use this prototype for dispatch or in-flight decision-making.
Model: spherical great-circle route sampled in short segments; wind corrected for along-track and crosswind components; time from ETP to departure is compared with time from ETP to destination. Earth radius: 3,440.065 NM. Inputs use degrees and decimal minutes (e.g. N68 59.4 W060 36.9). Default TAS is 436 kt (user-supplied planning assumption; adjustable). This version does not model temperature/altitude changes, acceleration, turn geometry, drift-down, terrain, airspace, fuel, or forecast wind variation.
01 · Import company OFP
Choose a text-based company operational flight plan PDF from the iPhone/iPad Files app. Extraction happens on this device; no PDF is uploaded to a server.
No OFP loaded.
02 · Review extracted route
One waypoint per line: FIX LATITUDE LONGITUDE. Coordinates may be compact (N5127.9 W00025.6) or degrees and decimal minutes (N51 27.9 W000 25.6). Check the order against your OFP navigation log. You can edit every line.
No route extracted yet.
03 · Diversion and performance
Wind is treated as constant and uniform for both diversions. Enter a representative route-average wind only if you have an approved source for it. The app does not infer FL100 winds from cruise-level or arrival descent data.
04 · Company route ETP result
ETP position on reviewed route
—
—
Distance from route start—
Distance to route end—
Distance to airport A—
Time to airport A—
Distance to airport B—
Time to airport B—
Important: This prototype calculates distances along the manually reviewed waypoint polyline, then estimates each diversion leg as a direct great-circle leg using one constant TAS and one constant wind. It does not reproduce the airline's approved OEI routing, drift-down, terrain/MEA constraints, aircraft performance, fuel model, or route-specific forecast winds. The result is not operationally approved and must not be used for dispatch or in-flight decisions.