Help from the people who build FLT.

FLT only counts a landing after the aircraft has sustained circuit height (about 400 feet above the field for a few seconds at flying speed) and then settled near the ground (below about 75 feet for a few seconds). Common reasons a landing is missed:

• The phone or watch lost GPS at the wrong moment, for example a phone deep in a bag under the airframe or a watch with the wrist held down.
• The altitude source was struggling: a large QNH error, or a barometer that had stopped reporting. FLT detects the second case but may take a few samples to recover.
• A very low circuit, or a landing straight off a long, shallow approach that never sustained circuit height as FLT defines it.

Repeated touch-and-goes on one approach each count once the aircraft hops at least about 25 feet off the runway and settles again. A single bounce or balloon is deliberately not counted twice. If you think a landing was missed, export the flight's telemetry as CSV and send it to us; every such flight improves the detector.

Because they are. The thresholds behind the scores are calibrated against the flights we have recorded so far and are still being refined as more flights are logged. The number is a useful, consistent measure of the same landing from flight to flight; it is not a certified assessment and it is not a substitute for your instructor's judgement.

No. The FIT app, which is coming soon, processes everything it reads from Apple Health on your iPhone and keeps it there: it is never synced to iCloud and never sent to us. Its estimates and written summaries are generated on the phone, using the on-device model of Apple Intelligence on a supported iPhone. The only thing that can leave the phone is the outcome of a check, Go, Caution or Stand down, with its time, and only if you have a Fyshh Aero account and turn that on, so it can sit beside the matching flight in your logbook. The privacy policy has the full list of what it reads and keeps.

No. In phone-only mode FLT records the whole flight from the iPhone alone: engine time, track, landings, go-arounds, landing and turn analysis, logbook and backup. The watch adds silent wrist reminders, auto-start when the aircraft begins to roll, complications, optional heart rate and a second, independent recording that is fused with the phone's.

Anywhere it can see the sky reasonably well: a mount, a shirt or jacket pocket, or the top of a flight bag. In a low-wing aircraft you will likely get good results even with the phone in your shorts or pants pocket, but on high-wing aircraft a direct line to the sky is your best option. Background location keeps the record going with the screen off. A phone buried under metal or in a footwell may lose GPS.

Automatic start is an Apple Watch function and arms the engine timer when FLT is the open app on your watch and your ground speed exceeds about 20 km/h. The phone does not auto-start on its own; it starts when the Apple Watch tells it to or when you tap Start on the phone screen. If you carry only a watch and it starts on a drive, stop the flight and it will not fragment your log: a stopped flight can be resumed within ten minutes, and a flight you did not mean to record can be deleted from the logbook.

From a flight's detail screen you can share its raw telemetry as a CSV file. The logbook itself can also be exported as CSV. Both use the standard iOS share sheet, so you can save to Files, AirDrop to a Mac or attach to an email.

Not unless you ask. FLT never rewrites a flight without your explicit permission, because you may already have copied its counts into your logbook. Open the flight and use Re-Analyse Flight to replay its telemetry through the current detection logic if you'd like to re-process that specific flight.

Only if you turn the feature on; it is off by default. With it on, the watch runs a workout session during the flight so heart rate is logged with each sample. The workout is discarded after landing unless you choose to save it to Health. With it off, FLT never requests access to any Health data from your watch or phone.

On your iPhone and, if you use one, your Apple Watch. With iCloud enabled, flights are mirrored to your own private iCloud database, so they are backed up and will appear on your other devices. If you have a Fyshh Aero account and turn on flight sync, a copy of each flight is also stored in your account on our servers in Sydney. See our privacy policy for more details on how your data is stored and managed.

A Fyshh Aero account is optional, and when you do sign in, FLT and the web portal ask for your password and then a one-time code sent to your e-mail address. The code is a second check that the person signing in controls that mailbox, and it is required on every sign-in rather than only the first.

Sync is off until you switch it on in Settings, and it needs a Fyshh Aero account with the Standard subscription. With it on, each flight is uploaded after it ends: the flight record, the telemetry (positions, altitudes, speeds and sensor values about once a second), the analysis computed on the phone, and the raw recordings. Each flight is either private, visible only to you, or school, visible to the instructors linked to you and your school's administrators. Nobody else can open a flight, and a private flight never appears to anyone but you. You can change a flight's visibility at any time, and deleting a flight removes it from the portal at once.

Only the people who could see the flight afterwards: the instructors linked to you and the administrators of the flight's school, on the web portal. Live streaming is a separate switch in the app, off by default, and a private flight cannot be watched by anyone. While it is on, the phone sends your position and flight state every few seconds; the stream is archived with the flight and removed when the flight is deleted.

While you are streaming, a linked instructor or school administrator can send a short message, such as a check-in or a pre-set phrase. It arrives on the phone and the watch shows it as a card with a haptic pattern that matches its urgency. You answer with a one-tap reply, such as OK, Busy or Returning; there is no free-text typing in flight. Messages are an aid for solo supervision, not an air-to-ground channel, and the radio always takes precedence.

With a Fyshh Aero account, the WX card shows the nearest aerodrome's latest report. Australian stations, including ATIS, come from Airservices Australia's NAIPS service; stations elsewhere, and any Australian station NAIPS cannot supply at the time, come from the NOAA Aviation Weather Center, and the card says which. The app sends your position to our server to find the nearest stations; the request to the weather source carries only the station identifier. The card is a convenience, not a substitute for a pre-flight briefing.

Either. Altitude, speed and pressure units are all selectable: feet or metres, knots or km/h, hPa or inHg.

The version of FLT currently in the App Store is an early release. Everything in it works, and it is free while we collect feedback from pilots in Australia and worldwide ahead of our full release. When subscriptions launch, early testers receive the Standard subscription free for life, so you will not lose existing functionality. See pricing.

FLT runs on an iPhone with iOS 26 or later, and an Apple Watch with watchOS 26 or later is optional. The app is a free download from the App Store, with the analysis features on the Standard subscription. See pricing.

COM is Fyshh Aero's optional cockpit device. It plugs into the aircraft's headphone circuit through a single cable, transcribes intercom and radio audio, puts clearances addressed to your call sign on the Apple Watch, and adds sensors the aircraft never carried. We are working towards flight testing in early 2027, and you can register for early access to fly with one before the first production run.

Yes. Fyshh Aero·FLT is the same app under its new name, from the same developer, at the same App Store listing. Your flights and settings carry over.