Every student learns the walkaround: kick the tyres, check the fuel, wiggle the control surfaces. Far fewer are taught to actually read the tech log before they sign for the aircraft, and that gap is where the A in PAVE quietly fails.
PAVE stands for Pilot, Aircraft, enVironment, External pressures, and the Aircraft line is not just "does it look airworthy." It is "what does the paperwork say happened to this specific airframe on its last few flights."
What the tech log actually is
The aircraft technical log is the running record of an airframe's defects, the maintenance carried out to clear them, and any items still open. The Kenya Civil Aviation Authority's Airworthiness Regulations (Legal Notice No. 40 of 2007) require operators to keep aircraft technical records current, and inspectors check them at every Certificate of Airworthiness renewal.
In the United States, the equivalent guidance sits in the FAA's Advisory Circular on maintenance records, which states plainly that discrepancy lists are part of the official maintenance record and must be complete. If an inspection turns something up, it goes in the log. It does not get fixed quietly and forgotten, and it does not get mentioned only verbally to the next pilot.
A training aircraft at a busy Wilson Airport school might fly six or seven times a day across different students and instructors. The tech log is the only thing that reliably survives the shift change.
"It flew yesterday" is not an airworthiness determination
The regulation that actually governs this, at least in the FAA framework that most Kenyan training syllabi still lean on, is 14 CFR 91.7. It puts the airworthiness call on the pilot in command, not on the maintenance department and not on the fact that three other students flew the aircraft that morning without incident.
The FAA's own interpretation is unambiguous: an aircraft with a current annual inspection but a known unsafe condition is not airworthy. A signed-off inspection is a snapshot from the past. A known defect written in the tech log this week overrides it.
This is the part most students skip past instinctively, because the social pressure runs the other way. Three people have flown the aircraft since the last entry, the instructor is waiting, and asking to see the tech log can feel like you are accusing someone of hiding something. You are not. You are doing the one part of the Aircraft check that the walkaround cannot do for you.
The discrepancy that becomes routine
The clearest illustration of what happens when a known discrepancy gets normalised instead of resolved is not a training accident, but it teaches the same lesson. In July 2007 a Cessna 310R operated by a corporate aviation department suffered a radar failure on descent, accompanied by the smell of burning electrical components, the day before its final flight.
The crew pulled the radar circuit breaker, the smell went away, and the aircraft was released to fly again the next day with that discrepancy known and unresolved. The NTSB's final report (AAR-09/01/SUM) found that decision, made by management, maintenance personnel, and the accident pilots together, was the probable cause of the in-flight fire that followed.
Nobody in that chain thought a burning smell should be flown around twice. What actually happened was smaller: a problem got a workaround instead of a fix, the workaround seemed to hold, and the aircraft flew again on that assumption. A training fleet is not a corporate flight department, but the mechanism is identical, and it scales down to a squeak, a sticky trim wheel, or a radio that "just needs a wiggle."
Inoperative equipment: placarded is not the same as fixed
Not every open item grounds the aircraft. FAR 91.213 allows a small non-turbine aircraft without a Master Minimum Equipment List to fly with some inoperative equipment, provided it is removed or deactivated, the cockpit control is placarded "Inoperative," and a pilot or qualified mechanic determines it is not a hazard for the flight being flown.
That is a real, legal path, not a loophole. The distinction that matters for a student is the difference between an item that has been through that process, placarded and logged, and an item that a fellow student mentioned in the crew room with no entry anywhere.
Only one of those has actually been evaluated against the regulation. The other is a rumour with wings.
The Kenyan flight-school tech log, in practice
Kenyan training fleets are typically small, shared, and busy, whether it is a C172 at Wilson doing circuits all morning or a PA-28 rotating between three instructors in a day. That shared-fleet model is efficient for the school and creates exactly the conditions where a defect gets mentioned rather than logged.
Add a culture where questioning an aircraft's fitness can feel like questioning your instructor's judgement, and a nervous student learns fast that the easier social move is to not ask. That instinct is precisely backwards from what PAVE is trying to build.
KCAA's inspection regime exists because operators keeping clean records is not automatic; the Airworthiness Regulations require it because without a written requirement, verbal handovers are what fill the gap. The AOPA Air Safety Institute's Richard G. McSpadden Report, the long-running successor to the Joseph T. Nall Report, puts mechanical causes behind roughly 18 percent of all general aviation accidents and 10 percent of fatal ones, with maintenance-related issues behind a meaningful share of those mechanical failures. That is not a reason to fear every aircraft. It is a reason the tech log line in PAVE is not decorative.
ICAO's version of the same rule
This is not a uniquely American requirement dressed up for a Kenyan audience. ICAO Annex 6, the global standard most national aviation authorities including KCAA align their own regulations against, requires operators to maintain technical records that capture an aircraft's status, including any deferred defects and the corrective action taken.
The detail worth noticing is "deferred," not "ignored." A defect can legitimately be deferred if the regulatory conditions for doing so are met and it is written down, which is exactly the placarding process FAR 91.213 describes. What Annex 6 does not permit, and no serious aviation authority does, is a defect that simply stops being mentioned because nobody wrote it anywhere.
Instructors carry this line too
A school's instructor sign-off culture sets the tone for whether students feel safe asking. If an instructor visibly checks the tech log before every lesson, a student learns that this is normal professional behaviour, not paranoia.
If an instructor waves it off with "it's fine, I flew it this morning," a student learns the opposite lesson, and that lesson outlives the one lesson it was said in. The review queue an instructor works through before signing off a student's solo or checkride readiness is a form of the same discipline: written evidence checked before a decision, not a verbal assurance accepted on trust.
A five-minute check before you accept the aircraft
This does not need to be adversarial or slow. Treat it as part of the handover, the same as checking fuel state:
- Ask to see the tech log, not just the fuel and Hobbs figures. A school with a healthy safety culture will hand it over without a second thought.
- Read the most recent open entries, not just the last signature. A signed-off entry tells you something was actioned; it does not tell you what the next open item says underneath it.
- Check any placarded inoperative items against what you were briefed. If the placard says something your instructor did not mention, ask before you accept the aircraft.
- Compare what the log says to what you feel on the walkaround. A vibration, a stiff control, or a smell that is not written down anywhere is the moment to stop and ask, not to assume someone else already checked.
- If anything does not add up, ask the instructor or the school's maintenance contact before start-up. A five-minute delay on the ground costs nothing. The same question airborne costs everything.
When to walk away
None of this is about grounding an aircraft over a scuffed paint chip. It is about recognising that some findings are not judgement calls at all. A known defect that affects the aircraft's structure, engine, or flight controls is not something a student, or even most instructors, should be negotiating around on the ramp.
If the tech log shows an open item you do not understand, or a defect that has been carried forward across multiple flights without clearance, the correct move is the same one FAR 91.7 assigns to the pilot in command: discontinue, or in a training context, decline the aircraft and ask. A good CFI (Certified Flight Instructor) will never make you feel foolish for asking to see the log first.
What pilots admit on the forums
Maintenance threads on pilot forums have a familiar rhythm. Someone asks whether a specific squeak or vibration is normal, and the replies split cleanly between "yes, all Cessnas do that" and "no, ground it, that killed someone I knew."
The confession that recurs more than any other is not about a dramatic failure. It is students admitting they flew an aircraft with a known niggle because everyone else seemed unbothered, and only afterwards, reading the tech log properly for the first time, realised the niggle had a paper trail going back weeks.
The Short Version
- The Aircraft line in PAVE is a paperwork check as much as a walkaround, and the tech log is where a known defect actually lives.
- FAR 91.7 puts the airworthiness call on the pilot in command; a valid inspection does not override a known unsafe condition.
- Placarded inoperative equipment under FAR 91.213 is a legal, evaluated status. A verbally-mentioned defect with no log entry is not the same thing.
- Shared training fleets create pressure to mention a defect quietly instead of logging it. Ask to see the tech log as a normal part of every handover.
- A known defect affecting structure, engine, or flight controls is not a judgement call to negotiate on the ramp.
AngaBrief's risk engine treats a known aircraft defect as a hard override: the assessment is forced to do_not_fly regardless of how well every other PAVE and IMSAFE line scores. The tool records that override in the audit log for the school and the instructor to see; it does not make the go or no-go decision, which stays with the pilot and their instructor, as it always must.
Key Takeaways
- Read the tech log at every handover, not just when something feels obviously wrong.
- A current inspection does not override a known unsafe condition under FAR 91.7.
- Placarded inoperative equipment has been evaluated; a rumoured defect with no log entry has not.
- A known defect in structure, engine, or flight controls means decline the aircraft and ask, not negotiate on the ramp.