Documentation

Flight records are the primary log of training activity. The Flights page works like a mark-sheet: instead of building rows from dropdowns, you run down the student's curriculum and tick each task as you would on a paper grade sheet.

How it works

1. Navigate to Flights in the sidebar and choose New Flight.
2. If you are an instructor, pick the student — the checklist then shows that student's curriculum (their active pursuit), grouped by ACS Area of Operation (or ABS section). Same-name students are disambiguated by email.
3. Each task line shows the student's prior status as dim context. Tap + Sat to add a green pill or − Unsat to add an orange one; tap multiple times to record several attempts on the same flight.
4. Sections are foldable, with an Expand all / Collapse all control, so you can hide the areas you aren't marking.
5. Add an optional title and Notes.
6. Tap Push flight once when you're done — the whole session posts in a single request.

Use this mode when a debrief reveals additional tasks to document, or when results are back-filled after the flight.

1. On Flights, choose Add Tasks to Existing and select a flight (listed date — student — title, most recent first).
2. The mark-sheet loads with the tasks already on that flight shown as non-deletable context, so you can see what's logged and add new marks alongside them.
3. Mark the additional tasks and push — the new marks are appended to the existing flight.

Marking an approach task opens an inline capture row: pick the approach from the offline-cached typeahead, and optionally expand Conditions to flag IMC, partial panel, or autopilot-coupled. A partial-panel non-precision approach automatically also credits the loss-of-primary-flight-instruments task, matching the analyzer's behavior. For the full glidepath/lateral analysis of an approach, score its GPS track in the Approach Analyzer and attach the result.

Selecting a flight opens its detail page (/flights/:id): the graded task list for that flight, an expandable analyzer view for any task that carries scored track data (map, deviation charts, gauges), and an inline instructor notes field that staff can edit and students see read-only.

The Print handout button produces a clean, one-flight page with the app navigation hidden — suitable for “Save as PDF” and handing to the student as a debrief sheet.

The mark-sheet is built to work in the airplane with no signal. Every mark is saved to a local draft on the device as you go, so closing or losing the app mid-flight never loses your work — reopening restores the in-progress flight.

When you push a flight while offline, the submission is queued locally and the app confirms it as pending. As soon as a connection returns, queued flights are sent automatically. A small pending sync indicator shows how many flights are waiting. Each submission carries a unique key, so a queued flight that also gets pushed manually can never create a duplicate.

Live Flight Capture records a flight from your device's GPS and detects and scores maneuvers as you fly, feeding the mark sheet in real time — with no track file to upload afterward. It runs entirely in the browser (a PWA), so use it on a tablet or phone in the aircraft.

Steps

1. On New Flight, choose the student (instructors) so the applicable maneuvers for that pursuit are loaded.
2. Open the Capture Live pane. On a tablet or desktop it sits as a panel to the right of the mark sheet (collapsed to a thin rail until you tap it); on a phone it fills the screen with a moving map.
3. Grant location permission when prompted.
4. Tap Start. Your track draws on the aeronautical chart — a VFR sectional, or the IFR low en-route chart for instrument students — as you fly.
5. Fly your maneuvers. Every few seconds the app re-scans the recent track and adds any detected maneuver to the timeline as a provisional mark on the sheet.
6. Tap End when finished, then submit the flight exactly like a normal New-Flight record. The captured marks and the full occurrence timeline are saved with it.

Detections stream into the timeline rail beside the map as you fly. Each occurrence shows its maneuver type, a Satisfactory / Unsatisfactory result, and the time it happened; repeat maneuvers of the same type group together with an S / U tally.

• Confirm / Reject — the instructor verifies each detection. Confirmed maneuvers become graded marks; rejected ones stay in the timeline struck through, so the full occurrence history is preserved for review and troubleshooting.
• Zoom to track — focuses the map on that occurrence's segment so you can see exactly which piece of the flight produced it.
• Scoring detail — opens a panel with the maneuver's profile chart and per-component score gauges (bank, heading, airspeed, and so on), so you can see why a maneuver was marked unsatisfactory.

The analyzer accepts GPS track files exported from ForeFlight or any app that produces a KML file (and GPX where enabled). The file must contain either a track with timestamps and altitude, or a coordinates-only path. ForeFlight recordings that carry native bank/pitch data unlock additional checks (such as stall detection) that a plain GPS track can't support.

1. Navigate to Analyzer in the sidebar.
2. Instructors: use the Analyzing for selector at the top to choose the student. The analysis then uses that student's curriculum and grading standard, and the saved results are attributed to them. Leave it on Myself to analyze your own flight.
3. Drag and drop a track file onto the upload zone, or click to open a file picker.
4. The file is parsed in the browser — nothing is uploaded at this point. The track displays on the map immediately.
5. Choose Auto or Manual detection mode.

Auto mode queries nearby airports from the CIFP database and tests every approach within range against the track. Detected segments are listed with the best-matching approach pre-selected.

Manual mode lets you type an airport identifier and select an approach from the list. Both modes support multiple rows for flights with several approaches.

1. After detection, each segment appears with its label and time. Review the approach subtype (e.g., ILS, RNAV-LPV, RNAV-LNAV) — you can override it if you flew an RNAV approach to LNAV minimums instead of LPV.
2. Click Score Selected. The analyzer scores each segment and automatically saves each result to the server.
3. Results appear per pass with: ACS Standard or Below ACS label, component score gauges (glidepath, lateral, altitude), the constraint crossing table, the approach map, and deviation charts.
4. Use the + Add to Flight button on any result to attach it to a flight record.

The Maneuver Analyzer uses the same KML track file as the approach analyzer. After uploading a track, the analyzer determines which maneuver types are applicable based on the certificate or rating you are pursuing, then detects and scores each maneuver found in the flight.

Steps

1. Upload a KML file in the Analyzer (the same upload used for approach analysis).
2. The analyzer computes your applicable maneuvers from your active pursuit (e.g., PPL-ASEL, IR, CPL-ASEL).
3. Toggle individual maneuver types on or off using the hint chips — each chip represents one ACS maneuver family.
4. Click Analyze Maneuvers. The analyzer smooths the GPS track, derives kinematics (turn rate, climb rate, bank angle estimates), and runs each detector.
5. Detected segments appear as result panels with component score gauges, raw metrics, and GPS limitation annotations.
6. Save individual results to the server, then optionally attach them to a flight record via + Add to Flight.

Maneuvers are grouped by category. Which ones appear depends on your active pursuit and aircraft class (single-engine vs. multi-engine). When an instructor analyzes for a selected student, the applicable set follows that student's pursuit.

Performance

• Steep Turns — 360° coordinated turns at 45° bank
• Straight & Level — sustained stable flight (altitude, heading, airspeed)
• Turn to Heading — roll out within ±10° of target heading
• Emergency Descent — rapid altitude loss at a controlled speed
• Stall — approach-to-stall / recovery (requires a track with native pitch data, e.g. ForeFlight)
• Steep Spiral — three 360° gliding turns with constant radius
• Chandelle — climbing 180° turn, max pitch at 90°
• Lazy Eight — symmetric climbing and descending turns through 180°

Ground Reference

• Turns Around a Point — constant-radius orbit maintaining altitude
• S-Turns — alternating semicircles across a line feature
• Rectangular Course — four-sided ground track with wind correction
• Eights on Pylons — figure-eight pivoting on two ground references at pivotal altitude

Takeoff / Landing

• Normal Takeoff — climb rate, centerline tracking, speed stability
• Normal Landing — stabilized approach, alignment, touchdown speed
• Go-Around — prompt climb initiation after rejected landing
• Traffic Pattern — four-leg rectangular circuit geometry
• Forward Slip — controlled cross-controlled descent to landing
• Power-Off 180 — power-off accuracy approach from abeam the touchdown point

Instrument

• Airspeed Change — accelerate/decelerate while maintaining altitude and heading
• Constant Airspeed Climb — sustained climb with speed control
• Rate Climb — climb at a target vertical speed (e.g., 500 fpm)
• Unusual Attitude Recovery — prompt recovery from nose-high or nose-low
• Holding Pattern — racetrack geometry, timing, altitude, speed
• Intercept & Track — intercept a radial/bearing and maintain tracking
• DME Arc — constant-radius arc at a specified DME distance
• Missed Approach — execute climb-out after descending to decision altitude

Each maneuver is scored on multiple component dimensions (e.g., altitude maintenance, bank angle, heading accuracy, airspeed control). Component scores range from 0 to 100 and are combined into an overall score. The maneuver meets ACS Standard only when every component individually passes its threshold.

Private vs. Commercial standard

Your active pursuit determines which ACS standard applies. IR and PPL pursuits use private pilot tolerances; CPL and ATP pursuits use tighter commercial tolerances.

Confidence rating

Each detected maneuver carries a confidence rating reflecting how certain the detector is that the GPS track actually represents this maneuver. Maneuvers with a clear GPS signature — steep turns, for instance, detected from heading change rate — rate high confidence, while maneuvers GPS cannot fully confirm, such as unusual attitude recovery, rate lower because GPS cannot verify actual aircraft attitude.

GPS limitations

Each component score is annotated with a GPS limitation notice explaining what GPS data can and cannot verify for that component. These annotations are saved with the result so they remain visible when reviewing historical data. Common limitations include:

• Bank angle — estimated from turn rate and groundspeed; actual bank angle is not measured by GPS
• Airspeed — GPS reports groundspeed only; indicated airspeed depends on wind, which is unknown
• Coordination — slip/skid and rudder inputs are invisible to GPS
• Power management — throttle position and RPM are not recorded

Many important maneuver errors are not detectable from GPS data — things like improper rudder coordination, fixation on instruments, or failure to clear the area. The Common Error Checklist lets instructors document these observations alongside the GPS-derived scores.

Instructor workflow

1. After a maneuver is detected and scored, the error checklist appears below the score gauges.
2. Check any errors the instructor observed during the maneuver.
3. Save the result — checked errors are persisted with the maneuver record.
4. Errors on previously saved results can be updated via the result detail view.

Student view

Students see checked errors as read-only items. This gives them visibility into what the instructor observed without the ability to modify the assessment.

Maneuver and approach detection is not perfect. If the analyzer misses a maneuver, miscategorizes it, or detects one that did not occur, you can submit feedback directly from the Analyzer page.

How to report

1. Click Report Issue after running detection (the button appears in the maneuver and approach result areas).
2. Select the category (maneuver or approach) using the toggle at the top of the dialog.
3. Choose a feedback type:
   • Missed — the maneuver was flown but not detected
   • Miscategorized — detected as the wrong type
   • False Positive — detected but the maneuver was not actually flown
4. For miscategorized and false positive reports, a Detected Segment dropdown pre-fills the start and end point indices from the segment that was incorrectly detected. For missed reports, set the point range manually using the slider or number inputs.
5. Select the expected type — for maneuvers, choose from the full list of maneuver types; for approaches, choose the approach subtype (ILS, LOC, RNAV-LPV, etc.).
6. For miscategorized reports, select detected as to indicate what the system incorrectly labeled the segment.
7. Add a description with any additional context (what you were flying, what you expected to see, etc.).
8. Review the map preview — the dialog shows the selected point range on a map with green (start) and red (end) markers, plus altitude labels. This helps verify you have selected the correct portion of the track.
9. Click Submit Feedback. The report is saved along with an excerpt of the GPS track data (the selected range plus ~50 points of context on each side, up to 2,000 points total).

What happens to feedback

Submitted reports enter a Pending status. Tenant admins and flight ops admins can review feedback in the Feedback tab under Tenant Settings, where they can:

• Filter by status: Pending, Investigating, Resolved, Won’t Fix
• Expand any item to see the full description, track metadata (altitude range, point count), and submission date
• Update the status and add resolution notes

The GPS track excerpt attached to each report is used by the development team to reproduce the detection issue and improve the algorithms.

For tenants that enable it, 61Insights implements the American Bonanza Society Air Safety Foundation Initial and Recurrent flight training records. Set ABS-Initial or ABS-Recurrent as the active pursuit and the Progress page, mark-sheet, and Maneuver Analyzer all reorient to the ABS catalog.

Two ways to log

• Per-flight — the regular mark-sheet works the same way, showing the ABS items instead of ACS tasks and grading them Satisfactory / Unsatisfactory.
• End-of-session form (/training-events/abs/new) — a single one-shot record capturing all ~50 items plus session metadata: aircraft, briefing and flight times, and the instructor signature.

Auto-assess from a track

Uploading a GPS/GPX track to the ABS form pre-populates each item's S/U from the analyzer where a detector exists for that item; items with no GPS signature (and the crosswind/short-field/soft-field variants) stay manual for the instructor to set.

Endorsements

From the completed items and session times, the platform derives the eligible endorsements — Flight Review, IPC, and WINGS — and shows them as advisory chips while you work; the saved record carries the authoritative result. The detail view prints to a clean facsimile of the paper ABS form.

Before scoring, the analyzer isolates the portion of the GPS track that actually represents the flown approach. It sets aside en-route and feeder-route data, trims the procedure-turn and base-turn flying that precedes final approach, and separates any missed-approach or go-around from the approach itself.

The aim is a clean final-approach segment — established inbound on course, from the approach's initial or intermediate fixes (or from the final approach fix when the recording starts later) down toward the runway — so that only genuine approach flying is measured. When a single file contains more than one approach, each is separated into its own scored pass.

Lateral performance is the perpendicular distance of each GPS fix from the approach centerline. The analyzer references that deviation to the full-scale appropriate to the type of approach flown:

• Precision and vertically-guided approaches (ILS, RNAV LPV) use an angular reference, so the allowable deviation narrows as the aircraft nears the runway — the way a localizer or LPV course actually behaves.
• Non-precision approaches (LOC, VOR, RNAV LNAV, NDB) use a fixed course width inside the final approach fix.

The deviation is evaluated against the ACS lateral tolerance for the flown approach, with a tighter standard applied for ATP-track pilots. Modest allowances are applied so that ordinary GPS position noise or a marginal signal doesn't, on its own, fail an otherwise well-flown approach.

Vertical performance is scored only for approaches with vertical guidance — ILS and RNAV approaches flown to LPV or LNAV/VNAV minimums. It compares the aircraft's altitude to the published glidepath along final approach, setting aside the landing flare and any missed-approach climb so those don't distort the result.

Deviation is evaluated against the ACS vertical tolerance for the approach. As with lateral scoring, small allowances absorb the altitude noise and datum differences inherent in GPS, so a stable, on-profile approach scores as one.

The analyzer uses published minimums from the FAA CIFP database to set the decision altitude or minimum descent altitude for the approach, and to check crossing altitudes at any step-down fixes along final approach.

Circling approach category

For a circling approach, the applicable minimum depends on the FAA approach category, which the analyzer derives from groundspeed when the track carries timestamps:

• Cat A: < 91 kt
• Cat B: 91–120 kt
• Cat C: 121–140 kt
• Cat D: ≥ 141 kt

Altitude checks

Crossing-altitude checks include a small tolerance in each direction to account for the difference between GPS-reported and barometric altitude and for normal altimetry error — the same reason a crossing altitude is flown to in practice, not to the exact foot.

The analyzer determines where the approach ends so that missed-approach or go-around flying isn't counted as part of the approach. Depending on the approach flown, it recognizes the end from the aircraft reaching the missed approach point, a climb away from the runway, or the track diverging from the final approach course.

Students are the primary users of the platform. Everything on a student's account is private — no other student can see their records. If you are training independently without a school affiliation, you are automatically enrolled in a personal solo account on first login.

Typical workflow

1. After each flight, log it under New Flight / Tasks with a title and one or more graded task entries.
2. Upload your GPS track (KML) in the Analyzer to score approaches (lateral, glidepath, altitude) and maneuvers (steep turns, ground reference, instrument tasks, etc.).
3. Attach approach and maneuver results to flight records to keep a complete debrief record.
4. Review ACS task progress on the Progress page.
5. Use the Dashboard calendar to track task volume and score trends over time.

Sidebar navigation

Dashboard · New Flight / Tasks · Analyzer · Progress

Instructors can view and create records for students assigned to them. Visibility is strictly limited to assigned students — data from other instructors' students is not visible.

Typical workflow

1. After a lesson, log the flight under New Flight / Tasks, selecting the student from the student picker.
2. Upload the KML in the Analyzer, score approaches and maneuvers, then attach results to the flight record.
3. Review the Common Error Checklist on each maneuver result to document observations that GPS cannot capture (coordination, power management, clearing turns, etc.).
4. Use the Students page to navigate to a student's record and review their flight history, analysis results, curriculum, and progress.
5. Use the Dashboard to see a summary of all assigned students' task performance.

Sidebar navigation

Dashboard · New Flight / Tasks · Analyzer · Students

Designed for chief instructors and schedulers. Flight ops admins see all students in the tenant, can create records for any of them, and manage instructor-student assignments — but cannot invite users or change membership roles.

Additional responsibilities vs. Instructor

• View and create records for any active student in the tenant, not just assigned students
• Access the Assignments page to pair and unpair instructors with students

Sidebar navigation

Dashboard · New Flight / Tasks · Analyzer · Students · Assignments

Full tenant control. Admins handle membership lifecycle: inviting users, adjusting roles, and configuring available training programs. All flight_ops_admin capabilities are included.

Additional responsibilities vs. Flight Ops Admin

• Invite new users by email with a specific role
• Revoke pending invitations before they are accepted
• Change any member's role at any time
• Deactivate student accounts (blocks login and uploads; preserves all historical data)
• Reactivate deactivated accounts
• Configure which training programs appear in the student pursuit selector

Sidebar navigation

Dashboard · New Flight / Tasks · Analyzer · Students · Assignments · Settings

A single account can hold memberships in multiple organizations simultaneously. Roles are independent per organization — you can be an instructor at one school and a student at another. The tenant switcher in the sidebar lets you switch between organizations. All data is fully scoped to the selected organization.

The Dashboard (/dashboard) is the student's primary performance overview with two main panels.

This Week

Stat cards appear for each task type (approach and maneuver) scored during the current ISO week, showing the min, mean, and max overall score. Cards are color-coded: green ≥ 80, yellow 60–79, orange < 60.

Activity Calendar

A month-at-a-glance calendar where each day with scored tasks shows the mean overall score, score range (min–max), and ACS pass rate (n/total). Clicking a day opens a detail panel listing each approach and maneuver result with its type, score, ACS label, and a link to the full result.

Solo users: My Course selector

Students on the solo tenant see a My Course dropdown above the weekly summary to select the certificate or rating they are pursuing. This sets the curriculum used in the Progress page. School-affiliated students have their pursuit set by an instructor or admin.

The Progress page (/progress) tracks ACS task completion against the curriculum for your active pursuit. A pursuit must be set — if none is set, a prompt directs you to set one.

Progress bar

A top-level bar shows the number and percentage of required tasks that have reached ACS Standard. Waived tasks (computed from already-held certificates) are excluded from the denominator and shown separately.

Task statuses

• Ready to test — demonstrated to ACS Standard consistently enough to be considered proficient
• Attempted — logged, but not yet enough to-standard demonstrations to be ready
• Not Started — no records found
• Waived — automatically waived because a prerequisite certificate is already held

“Ready to test” is proficiency-based rather than a single passing score: for ACS/FAA curricula it reflects the task being flown to standard across multiple distinct flights (a task shown just once, or several times on one flight, reads as still approaching ready); for the ABS training record the most recent attempt in the current cycle governs. The exact bar is tied to the curriculum and can be adjusted by the school in Tenant Settings. Expanding a task row shows the full evaluation history — dates, flight titles, scores, and links to results — with pills grouped by flight so “three good passes on one flight” reads differently from “three good passes across three flights.”

The ⓘ icon on each task opens a drawer with the full ACS knowledge, risk management, and skill standards for that task.

New Flight / Tasks (/flights)

Flights are logged on the mark-sheet. After a flight is pushed it appears in the student's history and on the Progress page; open any flight to see its detail view — the graded task list, expandable analyzer data for scored tasks, and instructor notes.

Analysis History (/history)

A table of all saved approach results, filterable by airport. Each row shows date, airport, approach label, overall score, and ACS label. Clicking a row opens the full Result Detail page with deviation charts, constraint table, and map. Each row has a + Flight button to attach the result to a flight record retroactively.

The Students page (/students) is the roster of all students visible to the current user. Instructors see only their assigned students. Flight ops admins and admins see all tenant members.

Each row shows name, email, and a status chip for non-active memberships: Pending (invited but not yet logged in) or Inactive (deactivated). Inactive rows are visually dimmed. Clicking any row opens that student's detail page.

The Student Detail page (/students/:studentId) is a tabbed view of everything logged for one student.

Flights tab

All flight records: date, title, task, score chip, and approach label/airport for approach tasks. Maneuver results attached to a flight appear as task entries with their ACS label.

Analysis tab

All approach and maneuver results: date, type, overall score, ACS label. Clicking a row opens the full Result Detail view.

Curriculum tab

Instructors and above can set the student's Pursuing certificate or rating, filtered to programs enabled by the tenant admin. The Already Holds section toggles which certificates the student already holds — this drives the waiver computation on the Progress tab. Instructors can save pursuit changes; changing held certificates requires admin role.

Progress tab

The same ACS task tracker shown on the student's Progress page: task status grouped by ACS Area, evaluation history per task, links to approach results.

Course History tab

A chronological log of every time the student's active pursuit was changed — previous value, new value, and date. Useful for tracking students who have transitioned between ratings (e.g., completed IR, now pursuing CPL).

When an instructor, flight_ops_admin, or admin loads the Dashboard it shows a Student Progress view — a task-oriented summary across all visible students — instead of the personal calendar.

Filter by Student

A dropdown lets you filter to a single student, yourself (Me), or view all students at once. Filtering to one student shows tasks directly; viewing all students shows one collapsible accordion per student.

Per-student accordion

Each accordion header shows the student's name, a curriculum progress fraction (n/total complete), and a two-tone progress bar: green for ACS-complete tasks, orange for attempted-but-not-yet-ACS tasks.

Task rows

Each task shows the task name, up to 5 recency dots (filled green for ACS Standard, hollow orange for Student), a count summary, and the most recent attempt date. Expanding shows up to 10 scored attempts with dates and links to approach results.

Tenant admins can customize the appearance of the platform for their organization. The Branding tab in Tenant Settings controls two properties that affect the entire app for all members of the tenant.

Logo URL

Provide a URL to a PNG or SVG image. The logo appears in the top-left header area where “61Insights” normally displays. Leave the field blank to show the default 61Insights wordmark. The logo is rendered at 36 px height and auto-scales width to maintain aspect ratio (max 220 px wide).

Appearance Preset

Two built-in presets control the full visual surface of the app:

• Aviation Light — light background, muted blue accents, high-contrast text. Best for daytime use and projection in classrooms.
• Aviation Dark — dark blue-black background with blue accents. Reduces eye strain during evening debriefs and matches cockpit lighting.

The preset drives header styling, card backgrounds, input fields, navigation, buttons, and text colors. A live preview panel in the Branding tab shows how each element will appear before you save.

Saving

Click Save Branding to apply changes. All tenant members will see the updated branding on their next page load. Changes are scoped to the tenant — members with memberships in other organizations will see each organization’s own branding when switching tenants.

The Programs tab controls which certificate and rating pursuits are available to students in the tenant. By default, all programs are enabled.

How it works

• Toggle individual programs on or off using the checkboxes. Use Select All or Clear All for bulk changes.
• Only enabled programs appear in the pursuit selector when an instructor or admin sets a student’s active pursuit.
• Solo-tenant users (students training independently) see only enabled programs in their My Course dropdown.
• Disabling a program does not affect students already pursuing it — they keep their current pursuit until it is explicitly changed.

Two school-level settings tune how strictly the platform judges performance, without changing the underlying FAA standards.

Marginal-signal grading

GPS-derived scoring can be penalized by measurement limits that have nothing to do with pilot skill — signal noise, sample-rate gaps, or the altitude-datum difference described under Accuracy & Limitations. With lenient grading enabled, a component that lands just under the bar for a measurement-limited reason can still pass when every other component is a clean pass. It softens false “below standard” results on otherwise well-flown work; it does not lower the ACS standard itself. (Solo/self-serve tenants default to the more permissive setting.)

Ready-to-test policy

The bar for a task to read ready to test on the Progress page is curriculum-based (see Progress Page) and can be adjusted here — for example, how many to-standard demonstrations across how many distinct flights a school wants before considering a student proficient.

The Feedback tab (visible to admins and flight ops admins) shows all detection feedback submitted by tenant members. This is the administrative side of the Report Issue feature in the Analyzer.

Reviewing feedback

• Each row shows the feedback type (Missed, Miscategorized, False Positive), category (maneuver or approach), expected type, submitter, date, and current status.
• Use the status filter dropdown to focus on Pending, Investigating, Resolved, or Won’t Fix items.
• Expand a row to see the full description, track metadata (total points, altitude range, excerpt indices), and resolution notes.

Updating status

1. Expand the feedback item.
2. Select a new status from the dropdown (Pending → Investigating → Resolved / Won’t Fix).
3. Add resolution notes explaining what was found or changed (up to 2,000 characters).
4. Click Update. The status change and notes are saved immediately.

Root admins managing other tenants can also access this tab from the Tenants management page.

The following issues arise from the nature of GPS data and the approximations in the scoring model. They are expected artifacts, not bugs.

GPS altitude vs. pressure altitude

ForeFlight and most GPS sources report WGS-84 ellipsoidal altitude, not the pressure altitude (MSL) used by approach plates. The difference between these two references (the geoid undulation) puts a small systematic bias on glidepath scoring, so even a well-flown ILS can carry a modest residual glidepath error for this reason alone.

No timestamps (LineString KML)

Some export formats produce a LineString without timestamps. In this case groundspeed cannot be computed, approach category is unknown, and the category-specific circling MDA cannot be selected.

Sparse track point density

A 1 Hz track at 100 kt produces a point every ~170 ft — adequate for final approach. Tracks at 0.1 Hz produce points ~1,700 ft apart. At that density, short excursions may be missed entirely (artificially good lateral score), and sparse tracks on curved segments like procedure turns can exaggerate cross-track error.

Magnetic vs. true course

Published approach courses are magnetic, while bearings computed from GPS latitude/longitude are referenced to true north. The analyzer corrects for magnetic variation where the navigation data allows; where it cannot, local magnetic variation can introduce a small systematic lateral offset.

ILS localizer beam model

The angular localizer model assumes an average antenna position for published ILS installations. Because actual antenna locations vary, the modeled beam can differ slightly from a specific installation — a minor effect far out that grows nearer the threshold.

Non-precision course width

Non-precision approaches use a default course-width reference when the navigation database doesn't publish a specific half-width. Because actual LOC/VOR course widths vary, that default can make the standard slightly stricter or more lenient than a particular approach's true structure.

Partial track recordings

If the GPS recording began after the initial approach fix was already crossed, the analyzer cannot find that fix passage and begins the scored segment at the final approach fix. The portion before the FAF is not included.

Pass splitting on shallow missed approaches

The analyzer separates repeated approaches by detecting a climb away from the threshold. A very gradual go-around — or a touch-and-go where altitude stays near threshold elevation — may not register as a split, causing two passes to be scored as one continuous track.

Maneuver heading scoring near north

Heading-based scores (straight & level, intercept & track, takeoff centerline tracking, etc.) correctly handle the 360°/0° wraparound. A heading of 359° and 1° are treated as 2° apart, not 358°.

Maneuver bank angle estimation

Bank angle is derived from turn rate and groundspeed using the coordinated turn formula. In turbulence or with significant crosswind, the estimate may diverge from actual bank angle. Steep turn bank angle scores should be interpreted as approximations.

Maneuver detection on long flights

Tracks from flights longer than two hours at 1 Hz produce over 7,200 data points. The analyzer processes these without issue, but dense tracks may surface more candidate segments that require manual review. Toggle off irrelevant maneuver types before analyzing to reduce noise.