Flight Risk Assessment Platform for US Private Aviation
We built Flight HQ — a role-based web platform that automates pre-flight risk assessment, shadow review, and final reporting.
Client & Context
Aero City Group provides customer-centric aviation services across training, rental, maintenance, and ownership.
The client needed to replace ad-hoc forms and email threads with a structured, auditable flow: pilots complete a standardized questionnaire, the system computes a Risk Level, and Flight HQ runs a shadow assessment before issuing a Final Report.
Aero City Group website (provided by the client; shown for context)
Goals
- 1Launch a single platform with Pilot and Admin roles and one sign-in flow.
- 2Streamline the assessment journey end-to-end: start → submit → shadow assessment → review/verify → mitigation if needed → final report.
- 3Automate PDF reporting and notifications with auditability.
Challenges
- Role clarity & safety-critical actions.
- Time-boxed submissions with draft persistence.
- Reliable outputs: consistent reports and delivery.
From Discovery to a Role-Based Risk Platform
Discovery
We captured roles, states, invite-only registration, single sign-in, and the end-to-end flow: Pilot submit → Admin shadow assessment → Review/Finalize → Verified/Mitigation.
Information Architecture
We defined one navigation model with role-scoped visibility: pilots see their profiles and assessments; admins see global listings, reviews, and management tools.
Mobile versions for Pilot’s and Admin’s homepages
Pilot’s and Aircraft profiles
We designed Pilot and Aircraft profiles. Data from these profiles is pre-filled in the start form.
Mobile versions for Pilot’s and Aircraft’s profiles
Pilot Journey
We designed the start form (airports, time, aircraft) prefilled from the profile, with draft autosave and a submission block outside the permitted window. The Risk Level displays immediately after submit.
The start form
Shadow Assessment
Admins perform a shadow assessment, then a Review screen shows both results, per-question deltas, totals, and a Finalize action to mark Verified or Mitigation needed.
Start shadow assessment screen
Final Report
We specified a read-only Final Report with flight details, both levels, and differences, downloadable as PDF and dispatched via email to the right parties.
Pilot’s Final report
Risks & How We Mitigated Them
Missing the deadline
Mitigation. We fixed a short, weekly milestone rhythm and only moved forward after each milestone was approved.
Decision bottleneck. Design/dev blocks while waiting for feedback
Mitigation. We booked fixed review windows and applied a “silent approval after 48 hours” rule for non-critical items.
Team member unavailability. A key designer or developer becomes unavailable
Mitigation. We kept specs and demo recordings up to date and assigned a backup owner for each critical area.
Compliance & Security
Source: @aerocitygroup
Results
Flight HQ moved from fragmented tools to one role-based platform. Pilots complete standardized pre-flight assessments; Flight HQ performs shadow review and issues Final Reports with consistent scoring and audit trails — improving clarity, speed, and confidence across operations.
