PAVE gets you airborne. It will not get you through what happens next.

Kenyan ground schools teach PAVE, IMSAFE, DECIDE and 3P as if they are four names for the same tool. They are not. Here is what each one is actually built for, and why mixing them up is why pilots freeze the moment conditions change mid-flight.

Open a Kenyan ground school binder and you will find at least four risk-management acronyms before you reach the end of Human Performance. PAVE, IMSAFE, DECIDE, 3P.

Ask most students which one they would actually reach for if the weather started closing in over the Rift Valley escarpment mid-flight, and you get a pause rather than an answer.

That pause is the real problem. It is not that students cannot recite the acronyms, most can recite all four for an exam without hesitating, but that nobody taught them these tools solve different problems at different moments in a flight.

The Short Version

PAVE and IMSAFE are snapshot tools. You run them once, before engine start, to decide whether to go at all.
DECIDE is a loop, not a snapshot, built for the moment something changes mid-flight and you need a structured response rather than a fresh risk assessment from scratch.
3P (Perceive, Process, Perform) is a continuous cycle that folds PAVE inside it, meant to run quietly throughout the flight rather than once at the start.
Kenyan ground school often teaches all four back to back with no explanation of when to reach for which, and that is a real training gap.
The fix is sequencing: PAVE and IMSAFE on the ground, 3P running at intervals in the air, DECIDE the moment something actually changes.

One family, not four competing systems

All four acronyms trace back to the same body of FAA material on Aeronautical Decision Making, most directly AC 60-22, Aeronautical Decision Making, and the later Risk Management Handbook, FAA-H-8083-2A. Kenyan flight training inherited this same lineage, the same route PAVE itself took into local syllabi.

They are not rival theories competing for a pilot's attention. Each one answers a different question, asked at a different point in a flight, and treating them as interchangeable synonyms is exactly what makes a pilot blank when the moment actually arrives.

PAVE and IMSAFE: the picture before you commit

We have covered PAVE and IMSAFE in detail elsewhere, so the short version here. Both are static checklists, run once, ideally sitting down before you drive to the aerodrome rather than standing at the aircraft door with the engine already primed.

They ask a single question with a single answer: given everything you know right now, should this flight happen at all? Once you answer yes and start the engine, PAVE and IMSAFE have done their job, and they were never built to answer what happens if something changes forty minutes into the flight.

DECIDE: the loop for when the picture changes

The DECIDE model exists precisely for that gap. It is a six-step loop, Detect, Estimate, Choose, Identify, Do, Evaluate, and unlike PAVE it is meant to run repeatedly, once for every meaningful change a pilot notices in flight.

Detect that something has changed. Cloud base lower than forecast, a NOTAM you missed, wildlife on the strip you planned to land at.
Estimate the significance. Is this a minor deviation you can absorb, or does it threaten the safety margin of the flight?
Choose a safe course of action from the options actually available, not necessarily the most convenient one.
Identify the specific actions needed to carry that choice out.
Do them, promptly, rather than continuing to deliberate once the choice is made.
Evaluate the result, because the loop does not end there. A new picture may call for running DECIDE again.

Picture a training cross-country from Wilson toward the Mara, routing near the Rift Valley escarpment. Forty minutes in, the cloud base that was comfortably above the terrain at departure has dropped, and the escarpment ahead is starting to disappear into it.

That is Detect. Estimate asks how much margin is actually left, not how the flight was planned to go, and Choose is the honest part: turn back to a known field, divert to a strip clear of the weather, or continue and hope it does not close further.

Only one of those three is a safe choice once the terrain risk is real. Identify and Do turn the choice into an actual heading and radio call, and Evaluate checks whether the new track is genuinely clear rather than assumed to be.

None of that six-step process is available inside PAVE. PAVE told you it was reasonable to depart; DECIDE is the tool for the moment departure conditions no longer hold.

3P: PAVE turned into a habit instead of a form

The 3P model, Perceive, Process, Perform, sits differently again. FAA training material built Perceive to be literally PAVE, run not once but continuously, at intervals throughout the flight rather than only before engine start.

Process leans on a second acronym, CARE: Consequences, Alternatives, Reality, External pressures, a short set of questions for weighing a risk once you have perceived it. Perform closes the loop with TEAM: Transfer, Eliminate, Accept, or Mitigate the risk, the same four options a risk manager in almost any safety-critical industry would recognise.

The practical difference from DECIDE is timing. 3P is proactive, a background check you run at intervals whether or not anything has obviously changed, at each waypoint on a cross-country or every fifteen to twenty minutes in the circuit.

DECIDE is reactive, triggered specifically by something 3P, or your own attention, has just detected. Think of 3P as the watch you keep running throughout the flight, and DECIDE as what you do the moment that watch flags something worth acting on.

Where Kenyan ground school gets this wrong

Here is my honest opinion, earned from watching how this material actually gets delivered rather than how the syllabus outline says it should be. Most Kenyan ground school sessions treat PAVE, IMSAFE, DECIDE and 3P as four items on the same page, taught in one sitting and tested with the same multiple-choice question format.

That produces a student who can define all four acronyms perfectly and still has no idea which one to reach for the first time weather actually closes in over unfamiliar terrain. Acronym recall is not the same skill as acronym application, and a written exam only tests the first one.

A better sequence is not hard to teach. PAVE and IMSAFE belong in the pre-flight brief, full stop, on paper, before the walkaround.

3P belongs in the air as a habit, a genuine check at each waypoint rather than a box ticked once at the start. DECIDE gets introduced specifically as the tool for the moment 3P, or plain observation, flags a real change, not as a fourth item to memorise alongside the other three.

Framed that way, a CFI (Certified Flight Instructor) is not teaching four competing checklists. They are teaching one continuous discipline with three distinct gears, and a student who understands the gears changes them without stopping to work out which acronym applies.

The umbrella all four sit under

All of this exists inside the wider discipline of single-pilot resource management, since a lone student or private pilot has to play every crew role that an airline crew divides between two or three people. We cover that ground in more depth in our guide to single-pilot resource management, and it is worth reading alongside this one rather than instead of it.

The short version for here: PAVE, IMSAFE, DECIDE and 3P are not separate subjects. They are the toolkit a single pilot uses to do, alone, what a full crew would otherwise share between two or three people.

What this looks like on an actual Kenyan training day

A student pre-flighting a navigation exercise from Wilson toward Kisumu, tracking through or around Rift Valley terrain, gets three distinct moments out of this toolkit rather than one long checklist.

On the ground at the school, before the walkaround, PAVE and IMSAFE decide whether the flight happens at all. In the air, a genuine 3P check at each turning point asks whether anything in that original picture, weather, fuel state, the pilot's own condition, has quietly shifted.

If haze building over Lake Victoria near the Kisumu approach starts eating into visibility beyond what was planned for, that is the moment DECIDE takes over from the background 3P check. Detect the change, estimate whether it threatens the flight, choose between pressing on, holding, or diverting, and act on that choice rather than continuing to fly toward deteriorating visibility while still deciding.

What pilots actually say about acronym overload. General aviation forums carry a recurring pattern worth describing rather than quoting directly, since none of it amounts to a verified source. Pilots learning ADM report memorising every framework cleanly for the written exam, then admitting, often much later, that the only thing they actually reached for in a genuine in-flight moment was whichever single step had been rehearsed until it was automatic, not the full acronym recited from memory. That matches what happens with any memorised procedure under real pressure: what survives is the part that was practised as a habit, not the part that was merely defined for a test.

Frequently asked questions

Do I need to memorise DECIDE and 3P separately from PAVE and IMSAFE?
Yes, but not as four unrelated lists. Learn PAVE and IMSAFE as your pre-flight snapshot, then learn DECIDE and 3P as the two ways you keep using that same information once you are airborne.

Is 3P replacing PAVE, since Perceive uses the same information?
No. 3P borrows PAVE's Perceive step wholesale and adds Process and Perform around it, which is exactly why the two feel confusingly similar in a syllabus that presents them side by side without explaining the relationship.

Which framework does AngaBrief use?
AngaBrief's pre-flight assessment is built around PAVE and IMSAFE specifically, because those are the pre-flight snapshot tools suited to a structured go/no-go form completed before departure. DECIDE and 3P are in-flight disciplines a pilot carries with them rather than something a ground-based tool can run mid-flight; AngaBrief is not a dispatch authority, and the go/no-go decision, on the ground and in the air, always rests with the pilot-in-command and their instructor.

What is the single most useful change a Kenyan ground school could make?
Teach the sequence, not just the acronyms: PAVE and IMSAFE before engine start, 3P as a running habit in the air, DECIDE the moment something actually changes. A student who understands why there are three tools, not four synonyms, uses the right one without hesitating.

Key Takeaways

PAVE and IMSAFE are one-time, pre-flight snapshots; they were never built to handle a change in conditions after departure.
DECIDE (Detect, Estimate, Choose, Identify, Do, Evaluate) is a loop for the specific moment something changes mid-flight, and it can run more than once in a single flight.
3P (Perceive, Process, Perform) folds PAVE into a continuous, background habit, using CARE to weigh a risk and TEAM to act on it.
Teaching all four acronyms in one sitting without explaining the sequence produces students who can define them but freeze when asked to apply one.
The practical sequence is PAVE and IMSAFE on the ground, 3P running at intervals in the air, and DECIDE the moment something actually changes.

Disclaimer: AngaBrief is a training and decision-support tool. It is not a dispatch authority. Final go/no-go authority rests with the Pilot in Command and the assigned Flight Instructor in accordance with KCAA regulations.