60 seconds
A briefing you can actually finish.
PAVE and IMSAFE in plain English on your phone. Fill it before walking to the aircraft. Save-as-you-go, refresh recovers state.
Get AngaBrief on your phone.
One-tap access on flight days. Installs as a real app on Android & desktop, “Add to Home Screen” on iOS Safari. No app store needed.
For Kenyan flight schools · KCAA-aligned
Every student briefed.
Every flight logged.
Every time.
Run your PAVE and IMSAFE on your phone before walking to the aircraft. Your instructor signs off in seconds. Your school keeps a permanent KCAA-ready record. Built for Kenyan flight schools.
Install AngaBrief on your phone for one-tap access on flight days. Works on Chromium browsers and via “Add to Home Screen” on iOS Safari.
Decision-support tool · Not a dispatch authority · Final go/no-go rests with PIC and instructor
Pre-flight assessmentready to submit
Banded verdict
Low · Elevated · High · Do not fly
- IMSAFE total0 – 25 pts
- PAVE Environment0 – 30 pts
- PAVE Pilot · Aircraft0 – 30 pts
- External pressures0 – 15 pts
Wind
—
Vis
—
DA
—
Decision-support tool · Final authority with PIC and instructor.
What you get
Three things every student pilot wants on flight days.
No black box
A risk score that explains itself.
0 to 100 with every contributing factor visible next to it. Density altitude, crosswind, fatigue — you see what counted and why.
Your record
A permanent record of your training.
Every brief you submit becomes part of your training trail. Your school's KCAA audit log. Your evidence of disciplined pre-flight habit.
Who uses AngaBrief
Four roles. Each does one thing well.
Roles are issued by the school admin via invite codes. Nobody self-promotes; everybody’s actions are logged.
Student
Authors the brief.
Picks the aircraft, route, and weather. Answers PAVE and IMSAFE. Submits to their assigned instructor. Cannot edit a submitted brief.
Instructor
Decides go / no-go.
Receives the queue. Approves, requests revision, or overrides with documented reasoning. Their sign-off is the legal artefact.
School admin
Runs the school on the platform.
Adds students and instructors via invites, manages the fleet, configures risk thresholds, exports the audit log for KCAA inspection.
Superadmin
Provisioning only.
Restricted to the AngaBrief team via database allowlist. Provisions schools, never touches a single school’s assessments.
How it works
Three steps. Phone in one hand, kneeboard in the other.
- STEP 01
Brief on your phone.
Before walking to the aircraft, work through the PAVE and IMSAFE prompts. Aerodrome data is pre-loaded from AIP Kenya. Manual weather entry, your instructor's call.
- STEP 02
Submit for sign-off.
Your assigned instructor sees the brief with a risk score and flagged items. They approve, request changes, or override — every decision recorded with reasoning.
- STEP 03
Keep the record.
Every brief becomes part of the school's KCAA-ready audit trail. UPDATE and DELETE are blocked at the database layer — nobody rewrites your training record.
The student experience
Students use it because it's faster than paper.
AngaBrief is built around how Kenyan student pilots actually work. The brief takes 60 seconds. The score is plain English. They get back to flying.
Step 4 of 8 · IMSAFE
Score 1 (none) to 5 (severe)
- Illness
- Medication
- Stress
- Alcohol
- Fatigue
- Emotion
STEP 01
The checklist.
PAVE and IMSAFE in plain language. Score each line one to five. Notes when something is worth flagging.
Risk score
Banded 0 – 100
Each contributing factor visible beside the gauge.
- Low0 – 20
- Elevated21 – 50
- High51 – 75
- Do not fly76 – 100
STEP 02
The verdict.
A single banded score with every contributing factor visible. No black box. No guesswork.
Instructor decision
- Approve· proceed with optional notes
- Request revision· returns the draft to the student
- Override· requires written reasoning
- Reject· logged with reasoning
Every decision carries identity, timestamp, and reasoning. Locked on submission. Edits prohibited at the database layer.
STEP 03
The sign-off.
Submission locks the brief. The instructor approves, requests revisions, or overrides — with written reasoning.
What you can verify
The claims a flight school can audit before signing.
- Risk engine
- Pure function with documented weights. 95% unit-test coverage on every band threshold and every contributing factor.
- Tenant isolation
- Row-Level Security policies in Postgres. pgTAP tests verify one school never reads another school's data.
- Append-only audit
- UPDATE and DELETE denied at the database role layer for the audit table. Even superadmin cannot rewrite history.
- AIP Kenya seed
- Twelve KCAA-licensed aerodromes seeded with field elevation, runway data, lighting, and fuel. Refreshed per AIRAC cycle.
- EU data residency
- Hosted on Supabase EU-Central (Frankfurt). Encrypted at rest and in transit. Daily point-in-time backups.
- KCAA-aligned export
- PDF export carries the regulatory disclaimer on every page, instructor identity, timestamp, and the AIP cycle used for the aerodrome data.
Built for KCAA
The compliance posture your inspector expects.
AngaBrief is designed around the artefacts a KCAA inspector actually asks for during an ATO audit. The format, the trail, and the retention posture are not optional features — they are how the product was architected from the database layer up.
- Regulator alignment
- Aligned with KCAA training and safety oversight requirements. AIP Kenya aerodrome data refreshed per AIRAC cycle (every 28 days).
- Audit format
- Audit logs match what inspectors expect — actor identity, action, before-state, after-state, IP, timestamp. PDF export with the regulatory disclaimer on every page.
- Append-only history
- UPDATE and DELETE on the audit table are denied at the Postgres role layer — even to the superadmin role. The trail is forensically intact.
- Instructor sign-offs
- Each decision carries the instructor's identity, timestamp, IP, and (for overrides) the written reasoning. Legally traceable.
- Tenant isolation
- Row-Level Security per school. pgTAP-tested per tenant on every release. One school never sees another school's data — by Postgres policy, not application code.
- Data residency
- Hosted on Supabase EU-Central (Frankfurt). Encrypted at rest and in transit. Daily backups with point-in-time recovery.