On this page
Flight Debrief
In the air you cannot see this software at all: your eyes are on the aircraft. The Flights page is where you find out afterwards what the device noticed, minute by minute, including the things it decided not to interrupt you with at the time.
One entry per flight
Each flight is listed with when it was, how long it lasted, and how many events it collected. The entries stay closed until you open one, because a debrief starts by picking the flight, not by scrolling past every event of every flight before it. A device that has never flown says so rather than showing an empty table.
The alerts you were never shown
Warnings reach your ground station as messages while you fly, but only the ones worth interrupting you for. An event marked not sent was held back deliberately: the device had already told you about that fault, and a second warning during a landing is noise, not information.
A fault that stays true collapses into one line with a count and the time it lasted until, so a camera that was dark for an hour is a single row rather than a hundred and fifty identical ones between you and the next real event.
Take the flight with you
A debrief usually happens away from the aircraft, so an open flight offers Download this flight. That gives you the whole timeline as a file to read at a desk, attach to a report, or send to someone who was not on the flight line.
Recording the video
Recording is separate from the debrief and lives with the camera, under Recording on the Streaming page. A camera does not record until it is asked to, so nothing fills the card behind your back, and each recording is listed with its size once it exists.
Flash your Pi in about 5 minutes
The Aircast Flasher downloads the image, sets Wi-Fi and hostname, and verifies the card.
On This Page