Documentation

The Lesson Plans page plans the next lesson for a student against your school's lesson syllabus — the planned sequence of lessons, each naming which ACS tasks it introduces and which it reinforces. That is a different thing from the ACS task list a student is graded on, which has no pedagogical order.

How it works

1. Open Lesson Plans and pick the student. The page suggests the next lesson — worked out from the flights actually logged, not from plans. It names the lesson by its title, its place in the course, and what the session should achieve.
2. Each suggested task carries a New or Review tag, depending on whether the lesson introduces it or reinforces it. Every task row also carries the same status pill and attempt history you'd see on Progress, judged for that plan's course, so how a task has gone before is on the plan itself. A task the student flew under another course still shows how it went.
3. Adjust the suggestion if you want to: edit the lesson title, add or remove objectives, add or drop tasks, set a date, or type a specific lesson number to plan a different lesson. Typing a number loads that lesson's tasks before you can create the plan; a number the syllabus doesn't have says so. A plan holds up to 60 tasks, and the task list shows the count.
4. Add Notes for the student and create the plan.

Where the syllabus has a fixed sequence, the page shows how many of its lessons are complete — “7 of 32 lessons complete” — the same count the student's My Syllabus shows. A lesson counts once it's completed with at least one of its core tasks done: flown on its flight, or, for a ground lesson, kept on the plan.

When there is nothing left to suggest, the page says why instead of showing an empty form. For example, every remaining lesson may already have a plan on the books (open one to fly it, or cancel one to re-plan). Once every lesson of a school syllabus is completed or credited, the suggestion becomes a Checkride prep session built from the tasks still unfinished, or a Mock checkride when none are left.

The plan is shared, then negotiated

There is deliberately no private draft and no publish toggle: the student sees the plan the moment it is created. An instructor who wants to think privately simply doesn't create the plan yet.

Each plan carries a discussion thread, so the lesson is negotiated before anyone flies it — the student can ask for a change, raise a concern, or confirm they're ready. The first reply moves the plan to Discussed, and either side can raise a point after it's approved. From there a plan moves through Approve, Start lesson, and Mark complete, or is Cancelled. A lesson started by mistake can go Back to not started.

Where the lesson stands

Each plan shows its status: Pending, Discussed, Approved, In progress, then Completed (or Cancelled). A completed lesson reads one of two ways:

• Completed · Flown — its flight recorded at least one task that was flown.
• Completed · Reviewed — it was held on the ground (a ground lesson, or a flight lesson turned into a ground session), or nothing on it was flown.

Whether a lesson was held on the ground is always a recorded fact — the lesson is a ground lesson, or it was closed out as a ground session. It is never guessed from how long the session took or how much it covered. The same two labels appear on the Dashboard calendar and in the day panel.

Once a lesson has a logged flight, its card links straight to it with View logged flight. A lesson whose closeout was recorded offline shows Waiting to sync, and its controls stay hidden until the closeout reaches the server, so the lesson can't be recorded twice.

A rated pilot flying to stay sharp isn't working through a course, so there is no “next lesson” in the usual sense. For a self-directed pilot with no course set, the app instead composes a cyclic proficiency course from the ratings that pilot holds.

1. Record the ratings you hold in the Ratings Held section of your Profile page. (An instructor can also record a rating for a student; you can always remove any entry on your own record, including one an instructor added.)
2. Your proficiency course is assembled from the published proficiency material for those ratings. Sessions are themed and small — for an instrument rating, for example, precision approaches and holds as one session, partial panel and unusual attitudes as another — rather than one grab-bag of everything.
3. Plan a session exactly as an instructor plans a lesson: the page suggests one, you adjust it, create it, and fly it.

Worth knowing

• Only your highest certificate in a class counts. If you hold overlapping certificates for the same aircraft class, the highest one governs — an ATP single-engine pilot doesn't also get the private and commercial material for that class.
• A cyclic course laps; it never completes. Coverage expires, so the session offered next is the one that has gone longest without being flown (with sessions you've had trouble on ranked ahead of ones you simply haven't flown lately). Because coverage is derived only from logged flights, planning a session does not refresh it.
• After a full lap, it keeps going. Once every session has been flown this cycle, the page offers Practice — one session of the tasks still unfinished, titled “Practice — ” followed by the first few of them — and it is worked out again after each session. When nothing is left unfinished it offers Open practice, a broad sample of what you've already shown. A proficiency course shows no lesson count, because it repeats.

If you haven't recorded any ratings yet, or if no proficiency material is published for the ratings you hold, the page tells you that rather than showing an empty course.

Some syllabi include ground lessons — study the student does off the airplane, on their own time. A ground lesson is studied, not flown, so it has its own short path and never goes near a mark sheet.

1. Plan it like any other lesson. In My Syllabus it reads Assigned for study.
2. Once the plan is approved and the student has done the work, they press Mark studied on the plan. The card shows the day it was studied, and My Syllabus reads Studied — awaiting review. Until the lesson is completed, the student can Undo it and the instructor can Send back for more work.
3. The instructor presses Mark complete. That completes the lesson directly — there is no flight to log and no scoring form — and it reads Completed · Reviewed.

A ground lesson has no Start lesson button, and no flight can be linked to it: a flight record would claim ACS work that was never flown.

Start lesson on a plan takes you to the mark sheet on Flights with that lesson's tasks already on it, tagged as coming from the plan and ready to score. You can also pick the lesson from the Planned lesson picker on New Flight. It offers only lessons a flight can still complete, and none is picked for you. A lesson that's already under way shows Resume flight on its plan, which takes you back to the open sheet.

Beside each task, the sheet shows the student's current status and their recent results on that task, from the server's record of logged flights.

One open flight per student at a time

From the moment you start a lesson until you push or discard it, that student has one open flight — and only one.

• The sheet is saved as you work, on the device and, whenever a connection allows, to the server. You can mark a whole lesson with no signal; a dead battery, a closed browser, or a reload does not lose it.
• Returning to that student resumes it. The sheet reappears headed by what it is — the lesson, when it was started, and how many tasks are still unscored (“Started Sep 8 · 2 tasks unscored”) — with Push and an explicit Discard. Picking the flight back up on a different device needs no takeover step: open it on whatever is to hand and keep going. If that flight was in fact already logged, the header offers Discard and a link to the logged flight instead of Push, so one lesson is never logged twice.
• You cannot start a second lesson for that student until the open one is pushed or discarded. The lesson picker refuses, right next to the Push and Discard that resolve it. This is what stops two lessons' tasks landing on one mark sheet — the confusing half-filled sheet this rule exists to prevent.
• Leaving the page with a sheet you haven't pushed warns you first, including on the back button and on closing the tab. The work is safe either way; the warning is there so you know the flight isn't logged yet.

A skipped task counts as resolved, not unscored, so it isn't in the “still unscored” count.

After you push

Pushing a new flight opens a short debrief: what was logged, task by task. If you plan lessons, Next lesson suggests the one after this and Plan it creates it. A task below standard today is carried into that plan only if you tick it. A flight still waiting to sync gets no suggestion yet — plan the next lesson from Lesson Plans once it has synced.

Weather turns, the aircraft goes down, the hour runs out. When a lesson planned a task you never got to, you record that explicitly rather than leaving the row blank.

1. Each unscored planned task carries a Skip control beside its Sat / Unsat buttons.
2. Skipping requires a reason from a short list — Weather, Aircraft, Ran out of time, Not ready for it, or Other with a note. Skip task stays disabled until one is picked, prompting “Pick a reason to record this skip.” The server refuses a reasonless skip as well, so a skip in the record always says why — which is the whole point of collecting them.
3. The task then shows a muted Skipped — Weather pill (or whichever reason you chose), distinct both from a score and from an untouched row. Undo skip puts the row back.

Wherever a logged flight's tasks are shown — the flight detail page, the student's Flights tab, the result card after a push — a skipped task reads the same way, “Skipped — <reason>”, never as a blank or a failing grade.

Skipping is one deliberate act per task. An instructor who didn't reach three tasks says so three times; there is no “skip the rest” button. The record is only worth having if somebody actually asserted it.

The requirement applies to tasks a lesson plan put on the sheet — those are the commitments. A row you added by hand and then decided against is simply removed; it was never a commitment.

Sometimes the lesson happens but nothing gets scored in the aircraft — a session written up afterward, or a flight lesson that couldn't be flown. Pressing Mark complete on a flight lesson with no flight logged against it therefore opens a short scoring form rather than simply closing the plan.

1. Set the Session date.
2. Give every task a disposition — a score, or a skip with a reason, exactly as on the mark sheet. Scoring a task you had skipped clears the skip.
3. Submit. That creates the session record and completes the lesson in one step.

There is no way out of the form without dispositioning every task, so nothing completes unassessed. If a mark sheet for that lesson is already open, what was scored there comes into the form, so nothing has to be scored twice. If that sheet's flight was already logged, the form links to it instead of recording a second session.

Weather or maintenance day: a ground session

When a flight lesson can't be flown, use Weather / MX day → ground session on its plan. It opens the same scoring form in ground mode:

• Score what you covered on the ground.
• Use Skip unscored: weather or Skip unscored: aircraft to skip every task still unscored, with that reason, in one step. Tasks you have already scored or skipped are left alone.

The record is titled “Ground session — <lesson title>” and carries a Ground session label on the flight detail page and the student's Flights tab. The lesson reads Completed · Reviewed.

Scores from a ground session count toward ACS progress and ready-to-test exactly as flown scores do. Skipped tasks still don't count. A lesson whose tasks were all skipped doesn't count as done in the syllabus, so it is offered again.

An abandoned flight must not need the instructor who started it — they may be off shift, on leave, or gone. Flight Ops Admins and Admins may therefore resume, complete, or discard any open flight in their school.

What they cannot do is disappear into the record.

• Resuming someone else's flight, the header names the instructor whose lesson it is and states that pushing it will be recorded as completed on their behalf. The confirm on Discard says the same thing, along with how many scored tasks would disappear. You should know that is what you are doing before you do it — not find out from a report later.
• The lesson stays attributed to the instructor whose lesson it was. Closing it out for them does not reassign it.
• The flight also records, explicitly, that it was completed by a delegate and by whom — and any task the delegate skips while closing out is attributed to the delegate, not to the instructor of record.

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 and recent results 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.

Schools that bill by the hour, or track maintenance on tach time, need the gauge readings from every engine start and shutdown. The mark sheet collects them as you fly, so nobody is reconstructing numbers from memory that evening.

Recording a reading

Each leg has an engine start and a shutdown, and each opens the same small sheet — “Leg 1 · engine start readings”, “Leg 1 · shutdown readings”, or simply “Flight start readings” and “Flight end readings” for a flight flown as one leg. Under the heading: “One photo with both gauges in frame, or type what they read. Hobbs or tach — either one is enough.”

• Take photo opens the camera. The photo is shrunk and stripped of its metadata on the device — no location, no camera details — and read on the device too. Nothing is sent anywhere to be interpreted.
• A number read confidently fills its field and is marked “read from photo”. Anything uncertain is left blank for you to type; typing over a value makes it yours.
• The sheet says what it is doing: “Reading the photo…”, then “Read the photo — check the values.” Where it cannot: “Couldn’t read the photo on this device. Type the values, or keep the photo for later.” The photo is kept either way.
• A number with no label beside it prompts once per flight for which gauge it is, Hobbs or Tach.
• At shutdown the sheet shows what the engine start read (“Engine start: Hobbs 1234.5 · Tach 987.6”), so a transposed digit is obvious while you can still look at the gauge.

A shutdown reading below its own engine start is refused as you type it, and the message names the earlier value.

On the sheet before you push

A strip along the mark sheet shows every moment at a glance: the value (“H 1234.5”), an asterisk where it came from a photo, the word photo where a photo is stored but no number was taken from it, or Add reading where there is nothing yet.

Afterwards

On the flight, each moment shows its reading, its photo as a thumbnail you can enlarge, or “Reading needed — see photo” where a photo was taken but no number was ever entered.

The flight’s instructor or an admin can fix a value with Correct. The dialog names the moment (“Correct leg 1 shutdown”), takes the instrument and the new value — “Leave empty to clear it” — and says plainly what will happen: “The change is kept in the flight’s reading history with your name and the time.”

Reading history sits under the readings, one line per change: “Leg 1 shutdown Hobbs: 1234.5 → 1235.0 · Jane Smith · 3:04 PM”. It is append-only — a correction is added to the record, never a quiet replacement of it. Corrections need a connection; offline, the button is disabled and says so.

An admin turns the requirement on for the whole school in Tenant Settings → Programs, under Engine readings: “Require engine readings on recorded flights”.

Selecting a flight opens its detail page (/flights/:id): the graded task list for that flight (skipped tasks read “Skipped — <reason>”, and a ground session carries a Ground session label), an expandable analyzer view for any task that carries scored track data (map, deviation charts, gauges), and an Analyzed maneuvers list and a track replay for a recorded or imported flight.

Instructor notes are a running log. Anyone who can see the flight — the student included — can Add note; each note shows who wrote it and when, oldest first. Notes can't be edited or deleted, so the log reads like a logbook. A note written before the log existed is shown above it as “Earlier note — no recorded author or time”.

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.

61Insights is built to work in the airplane with no signal. What you have already loaded stays readable on the device, and the work that matters most in the cockpit — scoring a lesson — never needs a connection.

One banner for the whole app

When you're offline, a single banner across the top of every page says so, and when the data on screen was last synced:

• “You're offline. Everything shown is from the last sync at <time>. Changes you make will sync when you're back online.”
• With nothing synced yet on this device: “You're offline. Showing data saved on this device.”

The banner also counts the changes waiting to sync, and once you're back online it reads “Syncing N changes…” until they have all gone through. It is the only offline notice — pages show what's saved on the device, as it is, underneath it.

The mark sheet works offline

Every mark is saved on the device as you go, so closing or losing the app mid-flight never loses your work — reopening restores the in-progress flight. Even with nothing saved on the device for that student, the sheet still lists their course's tasks to score. The status and recent results beside each task come back once you're online.

Offline, the push button reads Queue flight. The flight is kept on the device and sent automatically as soon as a connection returns. Each submission carries a unique key, so a queued flight that also gets pushed by hand can never create a duplicate. A lesson whose flight is queued isn't offered again until it has synced.

What syncs later

Three kinds of change are kept on the device and sent when you reconnect:

• a pushed flight;
• tasks added to an existing flight;
• a lesson closed out in its scoring form.

Other changes, such as creating a lesson plan or posting in its discussion, need a connection.

If the server refuses something that was queued, it is never thrown away. A banner — “1 saved session couldn't be synced” — lists it with the server's reason. Try again resends it. A lesson closeout offers Reopen scoring instead, so you can fix it in the form it was entered in. Discard asks first, because the device holds the only copy.

Your upcoming students, ready before you go

For instructors and admins, the app also keeps the students you're about to fly with on the device. After you sign in, when you reconnect, and again each day, it looks for students with an open lesson in the next 48 hours and saves their progress, their lesson plans, the upcoming lesson itself and their syllabus progress. It covers up to 10 students for an instructor and up to 50 for flight ops admins and admins, whose view is school-wide for things like stage checks. Soonest lessons come first.

So even with no signal at the airport you can open that student's row in Roster Progress, their plans on Lesson Plans, and the mark sheet for their lesson. A roster row you've opened before is also kept on the device.

When an instructor logs a lesson flight they graded, the student is asked how they think it went before they see those grades. Answering first is the whole point: a student who has already read “Unsat” can no longer tell you what they honestly thought.

The card

On the flight the student sees Your self-assessment: “Before you see your instructor’s grades for this flight: how did each task go?”, together with the date the grades appear regardless.

• Every graded task takes one of three answers: S, U, or Not sure.
• The hardest part (optional) — up to 500 characters, in the student’s own words.
• Overall confidence (optional) — 1 to 5, where 1 is not confident and 5 is very confident.

Submit stays disabled until every task has an answer, and the caption adds the point that matters: “‘Not sure’ is an answer.” Skip asks once more — “Skip it? You can’t do it later.” — because skipping is final.

With no signal the answer is held on the device and sent when the connection returns; the card says so, and the grades appear once it has gone.

What is hidden, and for how long

Until the student answers, the flight shows them everything except their instructor’s assessment of it: no task scores, no skip reasons, no analyzer verdicts or result links, no endorsements — and no instructor notes at all. The dashboard still shows the day, and offers a way into the self-assessment, but the flight counts toward no tally.

Hiding the written notes as well as the scores is deliberate: “Unsat on steep turns, repeat next lesson” gives the verdict away as plainly as the score does.

It reveals the moment the student submits or skips — and if they do neither, after seven days, on its own. Nothing is withheld indefinitely, and nothing waits on the instructor to release it.

What the instructor sees

Student’s self-assessment appears on the flight, and in short form on the lesson plan card: each task with its S, U or Not sure, the hardest part in the student’s words, and “Confidence: 4 of 5”. A student who skipped reads “The student skipped the self-assessment.” If they wrote about the hardest part, their instructor is told.

A bell in the header carries whatever is waiting for you in the school you are currently in. Its badge counts only what is unread and not muted.

The drawer

Opening the bell splits what is there into Needs you and Updates — things waiting on your action, and things simply worth knowing. Mark all read clears the badge, and anything already dealt with carries a small Done chip.

Opening an item takes you to the thing itself. When more are unread a bar offers Next (3 more) →, so you can walk the queue without coming back to the bell each time.

What you may be told

• A lesson flight is ready for your self-assessment — and a reminder if it is still waiting the next day.
• A new lesson plan for you; a plan of yours changed or approved; a new message on one.
• A lesson within 24 hours that nobody has approved yet.
• A student wrote about the hardest part of a flight.
• An analyzer review you were part of was resolved.
• Your flight review is coming due, or its date has gone by — only once you have entered the date on your Profile.
• Encouragement to keep training — when it has been a while since your last lesson, when nothing is booked after a lesson, or when you reach a milestone: a syllabus stage, a task flown to standard for the first time, being checkride-ready, 5, 10, 25, 50 or 100 lessons. Only when your school turns it on (you can still turn it off) or, training on your own, you turn it on yourself. At most one a week, and never between 21:00 and 8:00 as a push. Rolling out to schools over the coming weeks.

Choosing what reaches you

Notification preferences — a section of your Profile page, or the gear in the notifications drawer — offer “Show me, in the app and in the daily email:” with one checkbox for each kind above. Unticking one mutes it in both places at once: a muted kind is never listed, never counted in the badge, and never emailed.

Below those sits a Daily email switch, on by default: “One email a day at 7:00 your time, only when something needs you. It never includes grades or scores.” It goes out only when something is actually waiting, carries your school’s name and colors, and links each line to the thing itself. It also carries an Unsubscribe link, and a one-click unsubscribe your mail client’s own unsubscribe button can use. Following it confirms the change — “You won’t get the daily 61Insights email any more.” — and turning the Daily email switch back on resumes it. Unsubscribing stops the email only; notifications still reach you in the app.

Encouragement arrives in the app and as a push notification, never by email. Each kind of encouragement also has its own checkbox in Notification preferences, and the Encouragement to keep training switch turns all of them off; the daily email never carries it.

“7:00 your time” follows the time zone of the device you use the app on, picked up quietly — there is nothing to set.

Push notifications

In the Android app (1.2.0 and later), once you turn on encouragement or enter your flight review date, the app asks once whether it may send notifications. Allow it and your encouragement and flight review reminders also arrive as push notifications — never between 21:00 and 8:00 your time (they wait until 8:00). A milestone can show on your lock screen; a reminder's text is hidden there. Push notifications (all your phones) in Notification preferences turns them off on every phone you use, and so does Android's own notification setting for 61Insights on a single phone. Signing out stops that phone using its notification token, though that is best effort if the phone is offline.

Notification preferences need a connection; offline, the page says so rather than letting you edit them.

The app records your flight from the device's GPS (or a connected GDL90 receiver). The recording keeps running while you use other pages, and it survives a reload or a dead battery. Use it on a tablet or phone in the aircraft.

Steps

1. On New Flight, choose the student (instructors). The recording belongs to that student, and the picker locks to them until it is pushed or discarded.
2. Tap Engine start on the session bar. It shows ● REC, the leg clock and GPS health. Grant location permission when prompted.
3. Tap Shutdown when the engine stops. A flight can have up to 8 legs; start the engine again for the next leg.
4. No recording? After the flight, use import a track (KML or GPX) instead.
5. Before Push, confirm the ground time. It is prefilled as the session time minus block time, and you can edit it. Block time is calculated by the server from the legs.

Once the last leg is shut down (or a track is imported), the whole flight is analyzed on your device. Each task row on the mark sheet then shows what the analyzer found:

• Suggested S / U: the analyzer's result, which you can tap to use as your grade. It is never applied on its own.
• Analyzer agrees / differs: how the analyzer's result compares with the grade you gave.
• Not found / No detector: the maneuver wasn't found in the track, or there's no detector for that task.
• Also flown: maneuvers the analyzer found that aren't on this lesson, which you can add to the sheet.

• Replay: a flight's detail page shows the whole track on a map, with legs, gaps and each analyzed maneuver highlighted, and a scrubber to replay it at 1×, 10× or 60×. Flights you've opened are kept on your device for offline viewing.
• Trends: My Progress and Student detail chart each maneuver's score over time.
• Thumbnails: each flight gets a map thumbnail of its track over the sectional chart.

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.

Approach and procedure data follow the AIRAC cycle in effect. The FAA publishes each new cycle a few weeks early; 61Insights prepares the approach and procedure data ahead of the change but uses it only once the cycle takes effect, so a track is never scored against procedures that aren't in force yet. Minimums are shown for the cycle in effect. Each saved result records the cycle it was scored against.

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. Read the lessons your instructor has planned for you on Lesson Plans, and talk each one through in its discussion thread before you fly it. For a ground lesson, press Mark studied when you've done the work.
2. After each flight, log it under New Flight/Tasks with a title and one or more graded task entries (your instructor may log a lesson for you).
3. Upload your GPS track (KML) in the Analyzer to score approaches (lateral, glidepath, altitude) and maneuvers (steep turns, ground reference, instrument tasks, etc.).
4. Attach approach and maneuver results to flight records to keep a complete debrief record.
5. Follow your syllabus lesson by lesson in My Syllabus on the Dashboard, and your ACS task progress on My Progress.
6. Use the Dashboard calendar to track task volume, score trends and planned lessons over time.

A self-directed pilot plans their own sessions on Lesson Plans too — see Planning Your Own Proficiency.

Sidebar navigation

Dashboard · New Flight/Tasks · Analyzer · My Progress · Lesson Plans

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. Plan each student's next lesson on Lesson Plans and agree it with them in the plan's thread.
2. Fly it: Start lesson opens the mark sheet on New Flight/Tasks with the lesson's tasks on it. Score each task, skip with a reason any you didn't reach, and push the flight.
3. Upload the KML in the Analyzer, score approaches and maneuvers, then attach results to the flight record.
4. Review the Common Error Checklist on each maneuver result to document observations that GPS cannot capture (coordination, power management, clearing turns, etc.).
5. Use Roster Progress to see who's flying soon, who needs attention, and where each student is in their syllabus.
6. Use the Students page to navigate to a student's record and review their flight history, analysis results, curriculum, progress and syllabus.
7. Use the Dashboard for your upcoming lessons and a summary of your students' task performance.

Sidebar navigation

Dashboard · New Flight/Tasks · Analyzer · My Progress · Lesson Plans · Roster Progress · 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
• Give a student a head start in their syllabus, from Student detail → Syllabus
• Resume, complete or discard any open flight in the school — see Closing Out Someone Else’s Lesson
• Keep up to 50 upcoming students on the device for offline use, school-wide, rather than an instructor's 10 (see Working Offline & Sync)

Grading, overrides, sign-off, approving lesson plans and running the live mark sheet need the instructor role. If you used to grade as an admin, ask your school admin to add the instructor role (a Settings card lists who did this in the last 90 days).

Sidebar navigation

Dashboard · New Flight/Tasks · Analyzer · My Progress · Lesson Plans · Roster Progress · 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
• Set how many days without a lesson puts a student under Needs attention in Roster Progress
• Turn on Send engagement nudges to students (Tenant Settings → Programs): off by default; admins and flight ops (rolling out; the switch appears once it’s enabled for your school)

Grading, overrides, sign-off, approving lesson plans and running the live mark sheet need the instructor role. If you used to grade as an admin, ask your school admin to add the instructor role (a Settings card lists who did this in the last 90 days).

Sidebar navigation

Dashboard · New Flight/Tasks · Analyzer · My Progress · Lesson Plans · Roster Progress · 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 Profile page (/profile) is the one page about you, and the one place the things about you are edited. Four sections, saved together by a single Save:

• Name — the display name others see on your flights and plans. Leave it blank to use the name from your sign-in.
• Ratings Held — the certificates and ratings you already hold. These drive waivers against a syllabus, and they are what a proficiency course is composed from. (An instructor can also record a rating for a student; you can always remove any entry on your own record, including one an instructor added.)
• Course — the certificate or rating your lesson plans and flight evaluations run on. A self-directed pilot picks it here; leaving it on Proficiency (default) means the course is built from the ratings above instead. A school-affiliated student sees their course named here but does not set it — their school does.
• Notification preferences — the same per-kind mutes and Daily email switch described under Notifications. Where your school (or, training on your own, you) has turned it on, the same section carries Encouragement to keep training and, in the Android app, Push notifications (all your phones).

Each section is written only when you actually changed it, so saving your name alone costs nothing else. Saving needs a connection.

Currency

Below the form, with its own Save, sits Currency. Enter the date of your last flight review (14 CFR 61.56) and it shows “Due by 31 Oct 2028” — the last day of the 24th calendar month after the month of your review — or “Overdue since …” once that date has gone by. You are reminded in the app 60, 30 and 7 days before the due date and the day after it, each at 8:00 your time, in the notifications of every school you belong to. Clear removes the date and the reminders that carry it; changing the date replaces the old date’s reminders.

The same form greets you once on first sign-in as About you, where it can be skipped and filled in later. The course is stated rather than offered there — first sign-in is not the moment to enroll in a syllabus.

The Dashboard (/dashboard) is the student's primary overview: My Syllabus at the top when you're working a syllabus, then two performance 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). Planned lessons appear as markers on their day; a lesson has no score, so it never changes a day's numbers. 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, plus that day's lessons — where a completed lesson reads Completed · Flown or Completed · Reviewed.

Self-directed pilots: My Course

A self-directed pilot sees My Course above the weekly summary, naming the certificate or rating their lesson plans and flight evaluations actually run on. Proficiency means no certificate is set and the course is built from the ratings you hold instead. It is shown here, not chosen here — Change it in Profile beside it opens your Profile page, where the course sits with everything else about you. School-affiliated students have their course set by an instructor or admin.

My Syllabus, at the top of the Dashboard, shows your progress through your school's lesson syllabus lesson by lesson. It answers a different question from the Progress page: which lessons are done, rather than which ACS tasks you've shown to standard. Your instructor sees exactly the same record on the Syllabus tab of your student detail page.

The header

The syllabus name and how many of its lessons are complete — “7 of 32 lessons complete” — with separate bars for ground and flight lessons. Many syllabi put their ground lessons first. That is not a gate you have to clear before flying, so the two are never shown as one sequence.

Lessons

Lessons are grouped by stage, with the stage you're in open. A syllabus with only one stage is grouped into Ground lessons and Flight lessons instead. Each lesson is named by its own title and shows where it stands:

• Not started
• Planned — a plan is on the books, with its date and time
• Assigned for study — a ground lesson set for study
• Studied — awaiting review — you've marked a ground lesson studied, and your instructor hasn't completed it yet
• Completed — completed as written, with the day it was completed
• Completed · modified — completed, but one of the lesson's core tasks was left out. The row lists what was dropped (and anything added).
• Credited · head start — before the starting point your school set for you (see Giving a Student a Head Start)

A lesson counts as complete once its plan is completed with at least one of its core tasks done — flown on its flight, or, for a ground lesson, kept on the plan. A lesson whose tasks were all skipped doesn't count. A lesson flown together with another says so, naming the other by its title. Credited lessons count toward the total, alongside completed ones.

A core task dropped from a completed lesson is listed under “Still to fly — dropped from a completed lesson” until it is flown on a later flight.

When the syllabus is finished

Once every lesson is complete, the header reads “Syllabus complete — checkride readiness is now measured by ACS tasks” and links to your task progress. A finished syllabus is a scaffold completed, not a readiness verdict; readiness is measured by your ACS tasks from there.

The Progress page (My Progress, /progress) tracks ACS task completion against the curriculum for your active pursuit — or, for a self-directed pilot with no course set, the proficiency course built from the ratings you hold. With no course at all, a prompt directs you to set one.

Every status, count and history on this page is worked out by 61Insights each time a flight is logged, and the page shows that record as it stands — so you, your instructor, the mark sheet and the roster always see the same statuses.

Progress bar

A top-level bar shows how many of your course's required tasks are Ready to Test. Tasks waived by a certificate you already hold are not in the count, and are listed separately so you can see them.

Task statuses

• Ready to Test — demonstrated to ACS Standard consistently enough to meet the school's ready-to-test policy
• Approaching Ready — flown to standard, but not yet often enough, or on enough separate flights, to be ready
• Attempted — logged, but not yet flown to standard often enough to be approaching 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 (by default, more than one); for the ABS training record the most recent attempt in the current cycle governs. The exact bar is the school's policy and can be adjusted in Tenant Settings. Expanding a task row shows its recent evaluations — 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.” When there are older evaluations than the ones shown, the row says so.

• Ground sessions count. A task scored in a ground session counts toward progress and ready-to-test exactly as a flown one does.
• Skips are shown, never counted. A skipped task appears as a muted mark in its flight's group, labelled with its reason, and never counts as an attempt.
• Other courses. A task flown under another course isn't listed here; a lesson plan's task rows still show how it went.

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.

Roster Progress (/roster-progress) is the staff home page: every active student you can see, one row each, answering where are they, what's next, and do they need attention? Instructors see their assigned students; flight ops admins and admins see the whole school.

Syllabus or ACS competencies

A Syllabus | ACS competencies switch picks the view. Training runs on the syllabus, so that is the primary view:

• Syllabus — the student's current lesson by its title and stage; how many lessons are done, with a bar (none for a proficiency course, which repeats); “Last lesson 5 days ago”; the next planned lesson and when (“Next: <title>, <day and time>”); and, once the syllabus is finished, “Ready to test X/Y” from their ACS tasks. A student with no ordered course reads “No syllabus”.
• ACS competencies — each student's task-by-task standing: their course, last activity, and how many tasks are Ready to Test under your school's policy, with a bar.

Courses with ground and flight lessons

Where a syllabus mixes kinds of lesson — a block of ground lessons alongside the flight lessons, as most published courses have — the row names the next lesson of each kind, not merely the next one in the outline: “Next ground: Ground Lesson 3” beside the current flight lesson. A student given a head start into flight lesson 7 no longer reads as though they were sitting on ground lesson 1, and the ground work they still owe is named in its own right instead of hiding behind the flight line.

The progress bar is then segmented: one segment per kind, each as wide as that kind’s share of the course and filled by its own progress. A course of 40 ground and 10 flight lessons shows both honestly, and neither hides behind the other. The count beside it (“18 of 50 lessons”) is the course as a whole. A syllabus with a single kind of lesson keeps the plain bar.

This is generic rather than a special case for two kinds: a syllabus naming a third kind of lesson gets a third segment, and its own “next”, the day it is loaded.

Sort: Relevance, A–Z, Activity

Relevance (the default) puts students in three groups, in this order:

1. Flying today or tomorrow — soonest lesson first.
2. Needs attention — a student in a syllabus they haven't finished who has completed no lesson within your school's needs-attention window (14 days unless your school changes it), or who has nothing planned next. The student longest since their last lesson comes first.
3. Everyone else, most recently active first.

A student on a proficiency course is never listed under Needs attention: a rated pilot has no expected cadence. A student who has finished the syllabus stays with the recently active students.

A–Z sorts by name; Activity by the most recent activity. Your view and sort are remembered on this device.

The pills

In the Syllabus view, a pill on each row says why the student is where they are, in plain facts:

• “Today 2:00 PM” / “Tomorrow 9:30 AM” — a lesson coming up. “Today” and “tomorrow” follow your device's time zone.
• “No lesson in 21 days” (or “No lesson yet”) and “Nothing planned” — why a student is listed under Needs attention.
• “Syllabus complete” — every lesson is done.

The pills describe the schedule, never the student.

Open a row for detail

Opening a row shows the detail of the view you're in: the student's lesson list in Syllabus, or their ACS task detail in ACS competencies (where Hide tasks not yet introduced trims the list without changing the counts). Flip the switch with a row open and its detail follows. Detail loads when you open it, and once opened it is kept on this device for offline use. Students with a lesson in the next 48 hours are kept on the device ahead of time, so their rows open with no signal (see Working Offline & Sync).

A page at a time

The roster loads 25 students at a time. “Showing X of N” counts your whole roster, and the next page loads as you reach the bottom (Load more does the same). While you scroll, no student jumps between groups; an update to a student's row changes it in place. Offline, the footer says the rest will load when you're back online.

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. A skipped task reads “Skipped — <reason>”, and a ground session carries a Ground session 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, from the same record: 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).

Syllabus tab

The student's My Syllabus, exactly as they see it: lesson by lesson, with separate ground and flight counts. Flight ops admins and admins also see the Starting point control here (see Giving a Student a Head Start). When the student has no syllabus to show — no course, none loaded, or a proficiency course — the tab says why.

A student who arrives with prior training, or who shows they're ahead, shouldn't have to work through lessons they have already mastered. A head start sets the point in the syllabus where they begin.

Who can set it

Flight ops admins and admins, on Student detail → Syllabus. Instructors and the student see the effect — the credited lessons, and a note saying where the head start begins, who set it, when and why — but have no control.

How it works

1. Under Starting point, choose where the student starts in Start at.
   • In a syllabus with several stages you pick a stage, shown as “Stage 2 · lessons 12–20 — <its first lesson's title>”.
   • In a syllabus with a single stage you pick a lesson, by its title.
2. Press Set starting point and confirm. You can add an optional reason — for example, what the student has already shown.

Every earlier lesson the student hasn't already completed then reads Credited · head start. Lessons they really completed keep their real state. The next lesson suggested for them starts at the starting point. Clear removes the head start, and every lesson goes back to how it really stands.

When an instructor, flight_ops_admin, or admin loads the Dashboard it shows Upcoming Lessons and a Student Progress view instead of the personal calendar.

Upcoming Lessons

The next open lessons across your students over the coming two weeks, soonest first, each with its status. Pick a student in the filter to see only theirs.

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 row per student with logged tasks.

Per-student rows

Each row shows the student's name, “n/total ready to test”, and a progress bar split by status (Ready to Test, Approaching Ready, Attempted). The counts honour your school's ready-to-test policy. A student's tasks load when you open their row.

Task rows

Each task shows the task name, up to 5 recency dots (filled green for ACS Standard, hollow orange for below standard), the sats out of attempts (“1/3”), and the most recent attempt date. Expanding shows up to 10 scored attempts with dates and links to approach results.

Tenant admins see Billing in School Settings. The School plan is billed per instructor, on the highest number of instructors in the billing period: everyone who holds the instructor role counts, so remove instructors who have left. Admins and flight ops are included free up to 10; each admin beyond 10 is a second line on the invoice, Additional admins (beyond 10). Someone who is both an admin and an instructor counts once, as an instructor. The page shows this billing period's instructor count so far, the estimated amount, the beta credit and the total, the plan and its status, the next invoice date and the payment method (None needed during beta while the beta credit applies).

• Add payment method opens Stripe's secure page to add a card. We never see the card number.
• Manage billing and Invoices open Stripe's billing portal, where you can change the card, download invoices or cancel.
• Schools that pay by invoice receive each invoice by email from Stripe, due in 30 days.

If billing setup isn't finished, admins see a Billing setup incomplete notice; finish it from the Billing page within 7 days to keep School features.

The terms are in the School Subscription and Software License Agreement.

Every flight school starts as a Flight School of One: free, with 1 active instructor and up to 3 active students. Choose I'm a flight school the first time you sign in, or, if you already fly with 61Insights, choose Start a Flight School of One on your Profile page or on the card on your Solo dashboard. You become the school's admin and its instructor, and your own logbook stays as it is. Flight logging, the analyzer, grading, syllabus progress and each person's records are all included. Roster Progress (it shows a lock), engagement nudges, custom programs and school branding are part of the School plan, and you can invite an instructor only while the school has none.

Upgrade to School on the Billing page (School Settings) moves your school to the School plan: unlimited instructors and students and every School feature. During beta, upgrading is free. When something is not on your school's plan, the app says what it is: admins can upgrade, and everyone else sees Ask your school admin.

If a School-plan payment fails, your school keeps everything while it is retried (14 days for a card, 30 days after an invoice's due date), and admins see a banner. If it is still unpaid, the school moves to the Flight School of One plan: 3 active students and 1 active instructor, and no new staff (an instructor can be added only when the school has none). Nothing is deleted. The 3 most recently active students, the longest-serving instructor and every admin stay active; everyone else becomes inactive and can still sign in and view their own records. An admin can change this under Choose who stays active on the Billing page. Members shows Active students: 3 of 3; to add another, you are asked to Choose a student to deactivate. Upgrade to School restores every setting and brings back everyone who was made inactive by the move to the Flight School of One plan.

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.

Admins set when a student is listed under Needs attention in Roster Progress, with the Needs attention after N days without a lesson setting in Tenant Settings.

• A student in a syllabus who has completed no lesson in that many days, or has nothing planned next, is listed under Needs attention.
• Any whole number of days from 1 to 90; the default is 14.
• The change applies the next time the roster is loaded; nothing is recorded against a student.

At risk

Once engagement nudges are enabled, Roster Progress has an At risk chip. It lists the students who are under Needs attention because of no recent lesson or nothing planned — longest since a lesson first — and loads the rest of the roster by itself. Each row shows the last encouragement the student was sent (“Reminder · 5 d ago · opened”) and whether they came back (Came back or No response). A student on a recorded training break is listed as “On a break (weather) until …”, not at risk. When your school has engagement nudges off, the list says “Turn on engagement nudges in School Settings.” instead of the last-nudge column.

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 main pages have a short guided tour that points out what each part of the page does, using the page's own labels.

• First visit. The Dashboard, Roster Progress, New Flight/Tasks, Lesson Plans and the Analyzer each run their tour once, the first time you open them. When a page changes enough to be worth a new look, its tour runs once more.
• Any time. Press the ? button (“Show me around this page”) in the header to replay the tour for the page you're on. My Progress has a tour too, but it only opens from the ? button.
• Things not on screen yet. A tour shows only the parts of the page you can see now. Some things appear later — the debrief after you push a flight, a flight already open, Load more on the roster. Press ? again once they're on screen to see those steps too.
• Analyzer results. Once an approach is scored, a ? beside the result tabs walks through the verdict, the component scores and the deviation charts.

Tours show the steps that fit your role: a student and an instructor see different steps on the same 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.