How it works

A complete line observation program, start to finish.

Planning, observation, de-identification, analysis and follow-up in one controlled system.

Set up your department

Your administrator registers your FOM, GOM and SOPs with their revisions, selects the standards you work to, and edits the starting checklist so each item points to your own manual paragraphs.

Invite your team

Invitations go to named people with specific roles. Crew accounts are linked to their roster entry so they can see and acknowledge their own observations.

Plan observations

The schedule shows who is due based on your observation interval, by fleet. Standards Captains pick trips and crews in advance.

Observe and debrief

A guided form walks through pre-brief, each phase of flight, threat and error coding, recognition, an improvement opportunity and the debrief. A pre-brief is required before anything can be submitted.

Split and protect

On submit, the system writes two records. The completion record names the crew and trip and holds no performance data. The observation record holds the ratings and notes with the month only. Names, tails, routes and dates are removed from notes, and notes are encrypted.

Weekly batch release

Observations are held until the next weekly batch and released together, so results cannot be traced back to a single flight by timing.

Review and act

The safety committee sees trends by checklist item and threat and error code, reads de-identified notes, triages feedback, and records actions linked to standards references. Small groups are hidden so no individual can be singled out.

Report

Generate a standards report for any period. It lists every requirement in the standards you selected, how it is covered, the evidence count, linked actions and any gaps.