RotorLab logo RotorLabDocs

The flight page and legal hold

This page is part of My Record. It covers a single flight opened in full, and the legal hold that preserves it.

The flight page#

Every flight on the record has its own page. Open it from the date on a row of the Flights board, from the date on the flight's row in the logbook table, from the date of a flight in an aircraft's flight list, or from the flown day of a flagged flight on the Safety Management board and a hazard's page. The page gathers what the flight was in one place, so you never piece it together from the logbook, the aircraft and the analyzer.

  • The heading reads "Flight on" the day and the job or site, with an identity line under it, and a trail from Flights to the aircraft to the flight. Badges show Aircraft when filed, the aircraft's readiness as the records read when the flight was filed, and Pilot on the flight's day, the pilot's standing for that day, with an anchor badge that says whether an outside timestamp has answered for the flight. A line under them says when the records were read, for example "Read from the records when this flight was filed, Wed Oct 28, 2026, 14:05 CDT, not at takeoff.": a defect or occurrence recorded after landing and before filing is in that reading.
  • The header buttons: Report a problem and Record an occurrence sit in the header, with Flight report when you have read this flight's log, and More holds Compare with the previous flight, Place legal hold (for people who may place one), Replay, the logbook and the aircraft.
  • The log facet in the header's facts reads the log's state in the Flights board's words: Log analyzed, Log kept, not analyzed yet, Log kept, analysis queued, Log kept, being analyzed, Log kept, could not be analyzed, Log kept, too large to analyze or No log file.
  • The top card names the aircraft (linked to its record) and when and by whom it was flown, with how it was filed (from a log, by hand, or by a ground station), a legal hold mark when one applies, and the standing stamp. Three figures sit beside it: Minutes (with what the time is measured from), Landings (with the sorties) and Findings from the log.
  • A card above the details appears only when there is something to read first: the crash verdict from the log's analysis, outside standing when the flight was flown outside the pilot's standing (with the reason given; when none is given, Give the reason opens a sheet where the pilot, the person who filed it or an organization admin writes it, and the card redraws), and the advisory score when the flight read unusual against the aircraft's own earlier flights. The score never blocks anything.
  • The details list the aircraft, the pilot, the packs (each linked to its own page), the job, the mission, the site, when and where it took off and landed, night, line of sight, the maximum height in your units, the airspace at filing (in words, for example "Class D: an airspace authorization indicated when filed", or "Inside a standing flight restriction when filed"; national defense airspace is said to apply only while a NOTAM activates it), the crew, the conditions, the log format and when it was filed. Remarks follow when there are any.
  • For an aircraft recorded as flown only inside an FAA-recognized identification area, a line under the details reads the flight's recorded position against the FAA's list: inside, it names the area and says that 14 CFR 89.115(b) needs the aircraft and the person at the controls to stay inside it for the whole flight, and that only the recorded position was read; outside every area, or in one outside its recognized dates, it shows a finding saying so. A recorded position is not a clearance.
  • What it was for states the flight's purpose as filed, the call details for a call-out flight, and any gaps in what the flight records, with the service record when there is one. For a crowd monitoring flight, Crowd authorization shows the Record you named and Where it is kept; the record is a link when your role reads the register of authorizations, and a role that does not reads "A record". A record that has since been deleted reads "A record no longer on file". When the flight carries nothing, Edit it in the logbook opens the form where you can add it.
  • Site owner's approval appears on a US inspection flight, and on any flight that holds one. It works as the card on the job page does, for this flight alone. When the flight's job holds an approval, the card says so with a link and says that one saved here stays on this flight and does not copy or replace the job's. It stays with the flight and does not print on the flight record.
  • At Launch is its own card, below what needs attention, for a flight that landed from a sortie. It shows what the job and the records said when the sortie launched, to anyone who may read the warnings, and the one plain line to anyone else who reads the flight.
  • Log file lists each log kept with the flight, with its state (analyzed, analysis queued, being analyzed, could not be analyzed, too large to analyze or not analyzed yet), its size and how long it is kept, and Download. When a log has been read, the header offers Analyze this log, which opens it in the Log Analyzer (or Open the crash analysis first when the log carries a crash signature).
  • Data quality gives the log's own data-quality check: recording gaps, frozen sensors, or a log that ends in the air, or Data quality: clean.
  • Track draws a small picture of the flight's path, from its start to its end, where your organization keeps positions and your role may see them. RotorLab stores up to 400 points of the path when it reads the flight's log, so a flight whose log has not been read since then says "No track is stored for this flight yet." instead. The retention window that removes exact positions removes the stored path with them (see Retention). It does not appear in a list, a download or a log reply.
  • Occurrences about this flight lists the occurrences that name it, each linked to its record. You see it if you are an organization admin or your role reads safety records.
  • What the analysis found lists the log's findings by level, in your units, and then, under What the data says before the end of the log, what preceded the end of the log as the Crash Analyzer shows it: for example a vortex ring reading, judged against the aircraft type's frozen disc loading or the linked build's. The card's heading counts both. On some flights the findings keep the analyzer's own units. It needs the Crash Analyzer on your account or Fleet Health on the aircraft; without either, the card names the add-on.

Edit in the logbook opens the flight's form when you may edit it: you are an organization admin, or it is your own flight and your role manages flights. Otherwise the button reads Open in the logbook, and it is offered only where the logbook will open for you. Your own flight opens in the Logbook tab of My Record; a colleague's opens on their page under Crew, on Flights. Aircraft record opens the aircraft's page.

You can open the page of any flight in your organization when your role reads flights, and of any flight you flew or filed whatever your role. Any other flight is refused, and a flight of another organization is not found.

A legal hold preserves a flight for a preservation letter, a claim or an investigation. While a flight is on hold it keeps its stored log files and every copy of its precise position past every window, it cannot be voided, and nothing filed with it can be deleted: its stored logs, the checklist runs filed against it, and the documents and photos on the occurrence that named it.

Open the flight with edit. The Legal hold row on the form says whether the flight is on hold, since when, and why. An organization admin, or a member whose role carries Safety records: manage or Records custody: manage, sees Place legal hold on a flight that is not held and Lift hold on one that is. Both ask for a reason; the flight's history keeps every reason, and each is written to the activity log. A pilot cannot place or lift a hold, even on their own flight.

A flight is placed on hold automatically the moment an occurrence names it. A hold can also be placed by matter on the Retention page, covering an aircraft, a pilot, a job, a span of dates or every record; a flight it reaches shows Covered by the legal hold for the matter on its Legal hold row, and that hold is lifted on the Retention page, not from the flight. A held flight reads legal hold in the flight list, and its hold (whether it is held, since when, by whom and why, and the matter of a hold placed by matter) is on the flight in the organization export, in audit packages, and in the API's flight records.