A new opening, seen and heard. Aerolog opens differently now. A line of light draws across a dark screen, the dark lifts to your own display mode, the aircraft of the app's icon settles on its disc, and the app is there in about two and a half seconds, where the old opening took nearly four. A tap skips it, and with Reduce Motion on you get the finished picture and a plain dissolve. It starts dark in every mode. Until now the first half second of every launch was a blank screen in the device's own appearance, which is white whenever the device is in Light, even with Night chosen in Aerolog. A flight plan you import is prepared on a dial, with the same five stages beneath it. When the mission was ready the old screen began to leave, came back with its stages unticked and left again; a finished stage could still read FETCHING; and the line saying you can tap to skip was hidden under the dock. All three are put right. Both have a few short sounds: as Aerolog opens, as each stage of a plan you have just imported finishes, and when the mission is ready. They are quiet when your device is on Silent, they do not interrupt Aero's voice or your own audio, and Interface Sounds in Settings turns them off. Subscribing asks for one confirmation now. Aerolog used to add a message of its own after the App Store's; the App Store's is the only one. Coming from an earlier version? 4.1.4 taught Aero to say taxiway Tango rather than taxiway T; 4.1.3 was housekeeping for iOS 26; 4.1.1 put the TIMES block and your staff number and signature on the plan. The What's New in the app lists all of it.

Aero says it the way you would. Aero now reads a briefing the way a pilot says one. Every taxiway, stand, gate and holding point in a NOTAM is spelt, taxiway Tango rather than taxiway T, and Alpha, Bravo, Charlie for a list, and Aero writes the word itself so the transcript reads as the voice speaks. A runway named by both ends reads as runways zero nine left and two seven right instead of a slash; information K is information Kilo; a departure like BAYLI 1T, an approach like RNP Y and the weather in a report, such as -SHRA or FZFG, read as they are said. When the TAF has changed at several airports since you briefed, Aero says so once and names them, the TAF has changed at OMAA, OMDB and OMAL, in its opening and in an Aero Watch alert alike, and whatever it has no time for is counted, never dropped. The assistant that answers on your device with Apple Intelligence now follows the same voice rules as the cloud one: digits with their units, the spelling alphabet on the ground, no slash spoken. And airports are said by name where Aerolog knows it, Abu Dhabi rather than O M A A. Coming from an earlier version? 4.1.3 was housekeeping for iOS 26; 4.1.2 corrected one sentence of the Pilot's Guide; 4.1.1 put the TIMES block and your staff number and signature on the plan. The What's New in the app lists all of it.

Housekeeping, for iOS 26. Aerolog has needed iOS 26 since version 1.6.0, yet Aero still checked for it before answering on your device with Apple Intelligence, a check that could never fail. It is gone, and Aero now asks only whether Apple Intelligence is available, as in effect it always did. Nothing on screen looks or behaves differently, and the minimum stays iOS 26. Coming from an earlier version? 4.1.2 corrected one sentence of the Pilot's Guide; 4.1.1 put the TIMES block and your staff number and signature on the plan, and rebuilt the timer as a chronograph. The What's New in the app lists all of it.

One sentence in the guide, corrected. The Timer topic in the Pilot's Guide said that turning the countdown bezel gives a tap you can feel at each minute, on any device. An iPad has no way to give one, so the guide now says it of the iPhone. Found in our own reading of the guide, not reported. Nothing else in Aerolog changes. Coming from 4.1.0? 4.1.1 put the TIMES block and your staff number and signature on the plan, and rebuilt the timer as a chronograph. The What's New in the app lists all of it.

The times and your signature, on the plan. Fixed first, both shipped in 4.1.0: a countdown or stopwatch started on the Timer was lost when you moved to another space, and reprocessing the same flight plan cleared the takeoff time you had entered. The timer now keeps running wherever you are in Aerolog, and a Reprocess keeps the times you entered. The TIMES block is written where it is printed. Touch OFF BLOCK, TAKEOFF, LANDING or IN in the ACTUAL column and a keypad opens for that one time. TAKEOFF there is the takeoff you enter in ETA TIMES - one value, moving every ETA on the plan - and BLOCK TIME is worked out for you, IN less OFF BLOCK, across midnight when the block crosses it. Sign the plan on the S/N-SIGN line of the block fuel page: your staff number, and your signature - drawn with Apple Pencil on iPad, or your name typed, on any device. Your staff number is offered again on the next flight, filled in but unsigned. Your signature stays on this device with the flight: it is never sent to us, and never goes with a flight you hand to a colleague. The timer is rebuilt as a chronograph, in Pearl, Obsidian and Night. Set a countdown of your own by turning the bezel, 1 to 60 minutes, or by typing hours, minutes and seconds; the presets stay. Also: the debrief reads the TIMES block's LANDING, and Records says which time is missing when there is no debrief; a flight handed to you says what came with it, and its takeoff fills a blank card; and a Pilot's Guide topic opens wherever you touch its row.

The whole fuel check, on the plan. Fixed first: since 4.0, the app closed itself every time Aero finished reading the briefing; Aero's greeting could be spoken without being shown; and after several hundred entries the storage Aerolog shares with its widget could fill, so that entries stopped being logged. All three are fixed. Every fuel box your flight plan leaves blank can now be filled in where it is printed. Touch a row on the flight log and the keypad has an ABO field under AFOB: the totaliser's burn-off is inked into the ABO box, with ABO minus EBO in the FUEL box beside it. Touch the dotted line after PIC DISC, BLK FUEL or AFOB AT COMMENCEMENT OF FLIGHT on page 2 and that figure is inked on the line; when the block is below PLANNED MIN plus PIC DISC, the keypad quotes the plan's own rule. From those, each row shows UNACCOUNTED - what you started with, less what the totaliser burned, against what the gauges read, 0.0 when every kilogram is accounted for - and, when your block differs from the plan's, DIFF WITHOUT BLOCK beside the printed DIFF. Figures only; what they mean is the crew's call. Your flights are kept. Importing the next flight no longer loses the last one: Systems > Records > Flights opens each with its debrief and everything you wrote on it. Remove Flight now asks whether to keep the flight or delete it, and storage the app never gave back is given back. Hand a flight to a colleague by AirDrop - the plan, what you wrote, the takeoff time and your Pencil marks - and on their device, running this version, it opens as the same flight. What you wrote also survives importing the same plan again. The Lock Screen steps through the sector by the plan with the app closed and no network. And Aero Watch Alerts, off by default, can re-check the NOTAMs and weather you briefed when iOS gives the app time in the background - a bonus, never a guarantee.

One figure on the flight plan screen was wrong, in the generous direction. A LIDO flight plan prints the maximum takeoff weight twice: in the takeoff performance block on page one, where it is the weight the runway and the day's conditions would allow, and on the weights line beside MLAW and MZFW, where it is the aircraft's own limit. Aerolog read the first. The TOW bar and the margin behind the performance-limited takeoff advisory were therefore measured against a limit the aircraft cannot carry - 331.9 t where the aircraft allows 316.0, a margin 15.9 t too generous on the flight this was found on. It now reads the weights line, and falls back to the page-one figure only on a plan that prints nothing else. A flight already on your device keeps the figure it was imported with until you import it again. Nobody reported this. It was found by making the parser remember which printed line every figure came from, the groundwork for showing you that line in a coming release. Nothing else changes in 4.0.1.

The plan is the instrument. Nothing new sits above your OFP. The page itself is now written on: touch a row of the flight log and a keypad opens for that fix, and your fuel check and crossing time are inked into the columns the printout left for them. A wrong entry is written over; a struck-out one stays struck out. Every entry is kept against that exact fix and survives a relaunch. From those entries Mission knows it is airborne - the next fix by the plan, fuel against plan from your newest check, top of descent, and at a reclearance the fuel required to continue beside what your checks project. Everything is worked out on the device from the OFP and what you wrote. Nothing reads GPS. Write the landing on the destination row and Mission debriefs the flight - block and airborne time, fuel burned and fuel over destination against plan - and drafts the logbook entry, night time by civil twilight along the route you flew. Nothing reaches the logbook until you tap Save. On a wide iPad in landscape, Mission keeps its column and the rest of the screen is the plan, or whatever Mission opens, at full height. Apple Pencil marks on the plan stay with the flight. Fuel-check prompts at a cadence you choose are off by default and never need a network. Also corrected: a corrected takeoff time could become a time nobody typed; a wrapped STEPS line lost every level change after the first; the logbook's night time was a clock-hour guess in your phone's time zone; fuel over destination on two screens came from the wrong row; and the Theater's footer attributed imagery and terrain that nothing on the picture was drawn from.

Aerolog knows whose flight deck this is. Your name, your seat and the type you fly have been in the Logbook for a long time, and nothing outside that one screen ever read them - the briefing called you "the pilot" while your own answers sat unused on the device. Aero now knows who it is briefing, and the flight plan screen carries your rank before you load anything. Nothing new is asked of you. A profile already set in the Logbook is working now, and an empty one leaves the app exactly as it was. It does not guess, either: with no name entered you get no greeting rather than an invented one. Fuel and weight now read in your operator's unit. Every fuel and weight figure was labelled kilograms regardless of what your flight plan said - the unit was read off the document and discarded. Aerolog now reads it and keeps it, so a plan printed in pounds shows pounds. The default is to follow your flight plan exactly, which is the only setting where the figure on screen matches the figure on your paper digit for digit. Settings will convert to kilograms or pounds if you prefer, and a flight plan that declares no unit is left alone rather than guessed at.

Your entered times now belong to the flight you typed them on. The takeoff, diversion and reclearance times you enter on the OFP are per-flight entries. One typed on an earlier sector could still be sitting in the field when you loaded the next OFP, and had to be deleted by hand before you could enter the real one. Each entry now carries its flight, and loading a different one clears it, whatever route that OFP took into the app. This matters more than a stale field looks. The takeoff time is what anchors every Z time Aerolog shows you, so a leftover one from another sector quietly moves your waypoint times, the mission timeline, the threat board, your nav log ETAs and the watch face together - by the same amount, and every one of them still looking reasonable. Also in this release: Aerolog reads LIDO operational flight plans and refuses the formats it does not support, because a briefing built from a document the app misread would look exactly like a correct one. The check that tells those formats apart searched for its keywords anywhere on the cover page, including inside longer words, so a flight plan that was never a LIDO document could in principle have been taken for one. It now matches whole words only. Nothing was seen doing this; it was found by running the check against real airline flight plans published in accident investigations.

Your mission, on your wrist. Aerolog now has an Apple Watch app. The face carries your report countdown, the ETOPS entry countdown, your next fix and its ETA, fuel against plan, EFOB at destination, the worst threat on the board and the ride ahead — and nothing else, because a wrist is for glancing at rather than reading. It mirrors whatever flight is loaded on your phone and goes blank when you remove that flight, so it can never show you a sector you are no longer flying. Install it from the Watch app on your iPhone; there is nothing to configure. Also in this release: everything from 3.7.3, which brought Aerolog to iOS 27.

Ready for iOS 27. Aerolog is built against the iOS 27 SDK and tested on it, and it still runs on iOS 26 — the minimum has not moved, so updating your phone stays your decision. Nothing on screen looks or behaves differently. This release is housekeeping, and it is listed rather than hidden. The newer compiler found two faults that had been shipping quietly for several releases: an environment value that rebuilt itself on every read, which could make views redraw for no reason, and a pair of speech callbacks whose memory ownership read as a contradiction. Neither was anything you would have noticed. It also corrects a privacy declaration. In September the App Store privacy label, our published policy and the About screen were all updated to say plainly that the AI briefing and voice input send data off your device. The privacy file built into the app was missed, and still said nothing was collected. It now says the same as the other three. What the app sends has not changed — what changed is that every description of it finally matches.

Two numbers on screen were wrong. A takeoff time you typed on one flight stayed in the field and re-anchored the next one, so waypoint times on the Ride Quality sheet — and on the mission timeline, the threat board and your nav log — could sit hours away from your OFP. The entry now clears when a new flight plan is loaded, and a time that cannot belong to the flight in front of you is not used at all. Airport elevation came from a feed that publishes it in metres and was shown as feet, so every airport read about a third of its real height. It converts now, and prefers the published figure where an open aerodrome dataset has the airport. The runway list from that same feed had never decoded at all and silently showed nothing; it decodes too.

We were wrong about your voice, and this release fixes it. Aerolog told you spoken questions were transcribed on your device and that the audio never left it. That was not true. iOS sends speech to Apple to transcribe unless an app explicitly asks it not to, and Aerolog never asked. It asks now. On any device that can transcribe locally, the audio does not leave at all. Where a device cannot, iOS still sends it to Apple — and the About screen says so plainly instead of promising otherwise. Our privacy policy and App Store privacy label were corrected at the same time. Nothing else about the app changed. Your flight plan, your logbook and your backups behave exactly as before.

Choose the level the jet stream is drawn at. The upper wind layer used to draw your planned level and only that. It now carries a ladder — FL450, FL390, FL340, FL300, FL240 — so you can see what the wind is doing at the level you are thinking of asking for, and what leaving the plan would buy in knots along your own track. Your planned level is marked and is one tap away. Five rungs rather than a free-running dial, because the forecast model publishes wind on those discrete pressure surfaces. All five arrive in the same request the layer already made, so moving between them is instant and uses no extra data. Also in this release: since the layer first shipped it was reading your planned altitude in the wrong unit and drawing every flight at FL390 however it was planned. Corrected.

Two fixes: • The spoken briefing now says its numbers properly. A trip fuel of 54681 kg was being read aloud as “fifty-four-six-eighty-one”, with the unit dropped. Every quantity is now spoken in full and in units — ninety thousand one hundred kilograms, flight level three four zero, QNH one zero one seven, runway one zero. • The NOTAM list scrolls again. With a flight loaded, the NOTAMs tab drew its list and then would not move unless your finger happened to start on an airport heading. The whole card is now the tap target as well. Also in this release: a raw METAR read aloud now decodes its issue time, its cloud groups and its temperature over dewpoint instead of spelling them out, and number words no longer follow the device language.

The jet stream, on the map. • See where the jet is — the core line with its speed and level, drawn the way a significant weather chart draws it, with the shear boundary where the turbulence lives. • See what it is doing to your flight — the wind resolved onto your own track, tailwind and headwind along the route, and whether the level above or below reads better. • Or watch the air move: storm-scale wind ribbons and a full particle field across your corridor. Everything is drawn from real samples, and the map says how many, at what spacing and at what level. Where the wind was not sampled, nothing is drawn.

Fixes. • A flight your dispatcher marked NON-ETOPS is no longer described as an ETOPS flight — in the badge, in the briefing, or read aloud. • Aero's controls no longer disappear after a briefing finishes. The orb and the briefing button stay put. • Internal cleanup with no change to what you see.

Aerolog 3.5.0 puts real lightning on the map. • Storm cells now flash at a rate that means something. Where the GOES satellites can see — the Americas, the Atlantic, the eastern Pacific — Aerolog counts actual lightning flashes from the Geostationary Lightning Mapper and shows the rate. • Everywhere else, cells still animate, driven by the storm tops your flight plan states — and they say "DEPICTED" rather than showing a flash count nobody measured. A number only appears where lightning was actually observed. • Cells are drawn the way a satellite sees them: lit from inside, with the flash travelling through the cloud, the anvil sheared downwind by your planned winds, and the height built from the reported tops. • Volcanic ash on the map: volcanoes at orange and red aviation colour codes appear at their reported position. An ash cloud is drawn only where one was actually observed or forecast — never guessed from the colour code. • Volcanic Ash Advisories now decode, including the VAA-in-NOTAM form you usually receive. Where a message's own text and the advisory centre's observation disagree, you see both. • Fixed: ASHTAM items were labelled one step out of register with ICAO Annex 15, so a volcanic ash advisory centre's name could appear — and be read aloud — under an "aerodromes closed" heading. • Fixed: the airport search box on the World tab was sitting under a fade and looked blurred or switched off. • About now names every service that receives text from Aerolog, and every data source it reads. All briefing outputs remain advisory. Verify OFP, weather, NOTAMs, charts and company sources before use.

Aerolog 3.4.0 rebuilds the flight deck — and reads your whole OFP. • The sector, in order: threats read as a ranked list ordered by when you meet them, each carrying the fuel you'll have there — and the route chart follows whichever one you pick. • Your route, actually drawn: the plan view shows the ground track you filed, with waypoints and hazards, against a distance scale in nautical miles. • Fuel beside time: the Mission ruler and the route profile both carry planned fuel, with fuel over destination and final reserve marked. • A new look: Light, Dark and red-safe Night now share one accent language. Mission, Aero and Systems are rebuilt around what you're actually doing, and the command dock stands down while you read. • Text size everywhere: your device text-size setting now scales Aerolog's own type, not just system controls. • D-ATIS beyond the US: runway in use, transition level and approach decode for airports worldwide. Reports outside the US are overheard from ACARS, so each one shows where it came from and how old it is — and where the ATIS and METAR disagree on pressure, the METAR is named as the current figure. • An outage now says so: when a weather, NOTAM, pilot-report or wind source can't be reached, Aerolog tells you the source is unavailable instead of showing an empty result. A feed that's down no longer looks like clear skies. • What changed: re-import a revised OFP and every changed figure rolls old→new with delta chips. • Fuel waterfall and wind morph: watch block fuel decompose down to planned fuel over destination, and planned cruise winds morph into live forecasts with the headwind delta called out. • Weather then & now: flip airport weather between the dispatch-issued snapshot and live conditions. The OFP side works fully offline. • Deeper parsing: cost index, dispatcher, OFP revision, filed ATC route, reclearance plan, MEL/CDL items. G-AIRMET areas and pilot reports join the enroute picture; widgets and the watch gain EFOB at destination, ETOPS entry and ride band. All briefing outputs remain advisory. Verify OFP, weather, NOTAMs, charts and company sources before use.

Aerolog 3.3.0 is silky smooth and smarter about the ride — a measured performance round plus a turbulence-aware AI briefing. • Faster and cooler: measured Mission scrolling, precomputed flight data, and adaptive motion that steps back under power or thermal pressure • Turbulence-aware AI briefing: Aero reads your ride report and calls out the chop — how rough, where, and how long after takeoff — by voice or text • New mission preparation: an airplane now flies your progress and departs when your briefing is ready All briefing outputs remain advisory. Verify OFP, weather, NOTAMs, charts and company sources before use.

Aerolog 3.2.1 makes the whole app smoother and Aero more dependable. • Reliable AI briefings: no more context-window errors on large long-haul briefings — Aero now routes between on-device and cloud AI and retries automatically • Clearer voice: QNH values, aircraft types, sub-zero temperatures, Mach numbers and radio frequencies are now annunciated correctly • Silky-smooth performance: scrolling and animations retuned across the dock, loading screens, dashboard, briefing, map and logbook — even with big NOTAM-heavy flight plans • Hands-free Aero fixed: after the briefing or any answer, Aero's mic opens again on its own — just say "Aero" to keep talking. Ready prompt is now simply "Press Go to start the brief" • One-take launch: reopening with a saved flight runs a single continuous preparation from parse to ready — no flashes, no restarts All briefing outputs remain advisory. Verify OFP, weather, NOTAMs, charts and company sources before use.

Aerolog 3.2 brings a more cinematic, tactile and legible flight-deck experience to the entire app. • A new widebody Mission reveal appears after OFP import, then settles into a distraction-free static presentation • Pearl Light adds layered depth and clearer operational hierarchy, with Dark and red-safe Night appearances retained • Aeroelastic card interactions feel more tactile and fluid on high-refresh displays while respecting Reduce Motion • Operational text wraps and reflows more reliably at larger text sizes throughout the app • Threats and shared briefs now present threat facts and source evidence only, leaving countermeasure selection with the flight crew • Finite animation and reduced offscreen work make navigation smoother without adding idle motion

Aerolog EFB 3.1.2 makes TPC Threats more airline-realistic and easier to brief. • TPC Threats now use a CTWOF+ scan: C Charts, T Terrain/Traffic, W Weather, O Operational/GNSS, F Fuel, and + Human Factors • Charts are now a first-class threat family for Jeppesen/LIDO procedure, amendment and NOTAM-vs-chart conflicts • GPS/GNSS jamming and spoofing threats now appear under Operational/GNSS • GNSS countermeasures now brief position/time/FMS shift monitoring, raw VOR/DME/LOC/DME cross-checks, conventional ILS/VOR options, ATC notification and fuel protection • TAWS/EGPWS wording remains conservative: terrain alerts are treated as valid until aircraft/OEM procedures support otherwise • About now includes Aerolog Instagram, website and Telegram links • Carries forward AI briefing voice polish, native offer-code redemption and Ride Quality v2

Aerolog EFB 3.1.1 improves the AI briefing voice and carries forward Ride Quality v2. • Aero now speaks aviation briefing tokens with clearer cockpit phrasing • Ride signals such as SR=8 are read as shear rate eight • Flight levels such as FL320 are read as flight level three two zero • Elapsed times such as T+1h49m are read as takeoff plus one hour forty nine minutes, not metres • Zulu labels and briefing punctuation now produce better pauses in spoken briefings • Subscription page now supports native App Store offer-code redemption • After a valid offer code is redeemed, Aerolog refreshes subscription access automatically • Includes the 3.1.0 Ride Quality v2 update: NOAA/AWC WAFS EDR forecast/advisory confirmation, takeoff-time cabin-secure timing, planned departure (STD) plus taxi offset fallback and a more readable Ride Quality screen