[00:00:00.000] Welcome back, focus learners.

[00:00:01.720] Today, we're jumping right into a really fascinating explainer.

[00:00:05.260] We're dissecting a heavily documented real-world aviation case study that asks a pretty wild question.

[00:00:11.340] How does a completely routine scheduling disagreement over flight training end up ending a student's solo flights altogether?

[00:00:17.960] We're going to impartially map out exactly how this relationship broke down between a student pilot,

[00:00:22.260] his certified flight instructor, and the flight school's management.

[00:00:24.960] So let's just get right into it.

[00:00:26.660] Formal withdrawal of flight instruction and solo privileges.

[00:00:30.540] Those are some heavy words.

[00:00:31.820] This is from an email sent on September 1, 2026 by CFI Jose E. Capellan to his student, Dave.

[00:00:38.780] This document records the final step in the chronology we are examining.

[00:00:41.940] It states that the instructor relationship and previously authorized solo privileges were withdrawn effective September 1.

[00:00:47.780] So you might be wondering, how in the world did a simple scheduling request lead to this?

[00:00:52.320] Our main goal is to examine the sequence between an everyday conversation about booking an airplane and the later formal withdrawal.

[00:00:59.520] How did the disagreement develop so quickly?

[00:01:03.160] OK, let's dive into this timeline to really anchor ourselves.

[00:01:06.880] All of this happens in basically a single month.

[00:01:10.080] On August 2, Dave gets his solo endorsement.

[00:01:12.800] He flies solo that day and again the next day on August 3.

[00:01:16.720] Then there's a bit of a gap in his solo flying until August 29,

[00:01:20.560] when Dave and Jose go up for a dual instructional flight.

[00:01:23.960] The very next day, August 30, is when the scheduling disagreement happens.

[00:01:28.560] And by September 1, the record includes a formal withdrawal.

[00:01:31.880] Section 1, the baseline, a successful flight with caveats.

[00:01:36.480] To really make sense of this sudden escalation, we need to establish exactly where their relationship was right before the dispute.

[00:01:42.960] We're looking at that August 29th dual flight from their base at KAXH down to KCLL and back.

[00:01:48.640] What's really interesting is that the instructor initially noted that Dave flew great overall during that two plus hour flight.

[00:01:55.960] Dave does not recall being told during the postflight debrief that Jose no longer considered him ready for local solo flight.

[00:02:01.200] Dave also does not recall being told that another lesson was required before any further local solo flight.

[00:02:04.640] No contemporaneous written record was located reflecting either statement during that debrief.

[00:02:08.640] But, you know, flying great overall doesn't mean it was flawless.

[00:02:11.360] Jose later documented specific safety and proficiency concerns.

[00:02:15.760] He noted that Dave got very slow in his approach at KCLL, came in high on the return to KAXH,

[00:02:20.560] and required coaching through short final to stabilize the approach.

[00:02:24.800] In aviation, a solo student absolutely has to be able to fix these things independently.

[00:02:29.120] An instructor must evaluate speed, altitude, stability, and the student's ability to correct conditions independently.

[00:02:33.200] So an instructor has a serious duty to weigh these factors.

[00:02:36.240] These were specific concerns for an instructor to consider.

[00:02:38.880] Section 2, the disagreement, August 30th escalation.

[00:02:42.640] So let's move to the very next day, August 30th.

[00:02:45.040] Dave reaches out to practice some solo maneuvers.

[00:02:47.440] And what starts as just a simple question about plane availability suddenly

[00:02:50.960] morphs into this really tense debate about scheduling control.

[00:02:55.040] During this chat, Dave is expressing frustration because he's having a hard time getting

[00:02:59.040] consistent access to an aircraft.

[00:03:01.280] He actually mentions he might use other instructors just to fly more consistently.

[00:03:05.440] Jose then asks when his last solo was.

[00:03:08.320] Dave first suggested August 14 and then wrote August 2. The later-reviewed flight record identifies August 3 as the most recent solo. Jose replies,

[00:03:10.880] that's over three weeks ago, unable to authorize a solo flight.

[00:03:14.720] That timing is important to the chronology.

[00:03:16.640] This 27-day gap is the very first reason given for denying the request,

[00:03:20.800] after they had flown together the day before,

[00:03:23.680] and the school later confirmed they didn't even have a strict three-week rule on the books.

[00:03:27.760] Let's look at how this negotiation actually went down step by step.

[00:03:31.840] Dave originally wanted to do touch and goes at a totally different airport, K-L-B-X.

[00:03:37.280] Jose flags the safety concern about doing that solo.

[00:03:40.320] Totally fair.

[00:03:41.520] Dave actually accepts that, drops K-L-B-X,

[00:03:44.000] and narrows his request down strictly to familiar maneuvers

[00:03:46.880] and local touch and goes at their home base.

[00:03:49.120] Well, it was only after Dave actively narrowed this request

[00:03:52.400] and pushed back on what had changed since he was praised the day before

[00:03:55.120] that Jose then provides the specific slow and high safety concerns

[00:03:58.800] from the previous day as his more detailed explanation.

[00:04:02.240] Section 3. The Recorded Data.

[00:04:04.320] The Garmin consumer-device GPX record.

[00:04:06.640] Whenever human memories clash like this,

[00:04:08.560] it is so incredibly helpful to look at raw data.

[00:04:11.520] Luckily, that August 29th flight was recorded by a Garmin GPS.

[00:04:15.360] This recorded data has accuracy limits, but it can test broad characterizations

[00:04:18.160] that can put these conflicting stories to the test.

[00:04:20.960] 70.5 knots.

[00:04:22.800] This is the median ground speed recorded during that final approach at K-C-L-L.

[00:04:27.040] Remember, Jose said Dave got very slow here.

[00:04:30.800] The data here tells a really nuanced story.

[00:04:34.160] Because winds were light that day,

[00:04:35.920] a 70.5 knot median ground speed makes it kind of tough to argue

[00:04:39.760] that the data shows a sustained late-final ground-speed collapse.

[00:04:43.920] Now, to be fair, Garmin records ground speed,

[00:04:46.320] not the actual indicated air speed in the cockpit,

[00:04:48.880] and obviously it can't tell us who was actually on the controls.

[00:04:52.160] But it does limit the broad characterization

[00:04:54.240] that the airplane was very slow throughout the analyzed runway-aligned final.

[00:04:57.760] But what about the return flight where Jose said Dave came in too high?

[00:05:02.000] Well, the GPS gives us another number.

[00:05:04.240] 4.9 degrees.

[00:05:06.160] That is the calculated late approach descent angle.

[00:05:09.440] This illustrates how the recorded data provides different levels of support for different parts of the accounts.

[00:05:13.680] The published visual descent angle for that specific runway is 3.5 degrees.

[00:05:18.560] A 4.9 degree flight path is consistent with, and provides limited support for, Jose's late-high criticism.

[00:05:22.000] The available data is consistent with the airplane being high late in the approach

[00:05:24.640] and needed a steeper correction to make the runway.

[00:05:27.040] The data therefore supports parts of both the student's

[00:05:29.920] and the instructor's accounts are grounded in actual facts.

[00:05:33.520] Section 4, escalation to management.

[00:05:36.080] The booking discrepancy.

[00:05:37.680] With the two of them essentially deadlocked,

[00:05:40.320] Dave takes the issue to gem aviation management.

[00:05:43.120] He speaks with a rep named Glenn McDonald,

[00:05:45.040] just hoping to find a way forward.

[00:05:46.880] The exchange identifies a significant scheduling-process discrepancy.

[00:05:50.720] Dave says he understood that he needed to go through his instructor for scheduling,

[00:05:54.720] that he had to text Jose to find out when planes were free.

[00:05:57.760] But Glenn tells him that endorsed students can actually just look up availability

[00:06:01.200] and book solo flights themselves

[00:06:02.960] directly through an app called Flight Schedule Pro.

[00:06:05.440] That is an important scheduling disclosure.

[00:06:07.520] I mean, if Dave had known he could just book it directly,

[00:06:10.320] that whole initial argument on August 30th over aircraft availability

[00:06:13.920] might have never happened.

[00:06:15.360] But right when this misunderstanding is cleared up,

[00:06:17.600] there's this jarring tonal shift.

[00:06:19.840] Dave asks if he can just use his existing endorsement

[00:06:22.480] to go ahead and book solo time in the app.

[00:06:24.880] Glenn's response?

[00:06:26.080] Jose has withdrawn his endorsement.

[00:06:28.400] After Dave asks to use this direct-booking method,

[00:06:32.240] Glenn states that Jose had withdrawn the endorsement.

[00:06:37.760] Section 5, the competing interpretations.

[00:06:42.080] We're now looking at a scenario with two entirely different,

[00:06:45.360] logically sound ways to view this exact same sequence of events.

[00:06:50.080] Let's steelman both sides equally here.

[00:06:52.560] On one side, you have the reactive escalation theory.

[00:06:55.440] The timing raises questions for Dave.

[00:06:57.600] Dave challenged the scheduling process, mentioned exploring other instructors,

[00:07:01.280] and the stated basis developed before the later written withdrawal.

[00:07:04.960] But on the other hand, you have the conservative safety theory.

[00:07:07.840] Instructors have the ultimate safety authority, period.

[00:07:10.720] Jose stated that his decision was based on

[00:07:12.240] his observations during the August 29 flight

[00:07:14.400] and made a strict conservative decision

[00:07:16.320] that Dave simply needed more dual instruction before going up alone again.

[00:07:19.680] The specific safety concerns remain evidence favorable to Jose's stated assessment.

[00:07:23.280] As we wrap this up,

[00:07:24.320] there are still questions the available record does not answer.

[00:07:28.320] What was actually said in that August 29 debrief?

[00:07:31.200] Was the whole three-week scheduling gap thing a genuine misunderstanding,

[00:07:34.640] or an initial shorthand explanation?

[00:07:36.800] We also know from the source material that earlier on,

[00:07:39.200] there were some instructional billing errors totaling about $162.

[00:07:42.960] They got corrected,

[00:07:43.680] but that definitely eroded Dave's baseline trust right from the start.

[00:07:47.040] Plus, Dave actually reached out to the local FAA flight standards district office

[00:07:50.880] for official guidance on exactly how an endorsement can legally be withdrawn.

[00:07:54.960] The inspector later advised Dave not to continue solo under the prior authorization, and the cited McHenry interpretation explains that another qualified instructor may issue a later endorsement after satisfying the applicable requirements.

[00:07:59.040] So I want to leave you with this final question.

[00:08:02.000] Was this a necessary safety intervention by a cautious instructor,

[00:08:05.520] or a reactive escalation sparked by a fight over scheduling control?

[00:08:10.000] While data can map a flight path down to the decimal,

[00:08:12.560] it simply cannot record human intent.

[00:08:15.040] The objective facts support parts of both stories,

[00:08:17.520] and the available record does not establish Jose's subjective motive.

[00:08:20.880] It shows how quickly a scheduling dispute can end one training relationship and the prior solo arrangement, even while other instructors or schools remain available.

[00:08:26.240] Thank you so much for joining me on this explainer.

[00:08:28.800] Keep asking questions, keep looking at the data, and we will see you next time.