N22UP did not enter Phase 1 with a vague goal of simply flying forty hours and hoping a complete test program happened somewhere along the way. The plan was to use the newer task-based approach and treat the operating limitations sheet as the real end product.
That distinction matters because a task-based program changes the question from “How much time have I logged?” to “What have I actually demonstrated?” For a brand-new airplane, hours still matter. Break-in still matters. Repetition still matters. But the purpose of those hours is to answer a structured set of questions about the airplane rather than to accumulate time for its own sake.
Why I wanted the task-based path
By the time the special airworthiness certificate was issued on May 25, 2023, the airplane already had a defined test agenda waiting for it. I was not trying to invent a Phase 1 plan in the cockpit. I wanted a framework that matched the way I think about flying and maintenance:
- Break the work into specific tasks.
- Document what each flight was supposed to answer.
- Carry the results forward into the final operating numbers.
That approach fit the airplane and it fit the mission. N22UP was a fresh RV-8 with a brand-new engine, a new panel, and the usual list of first-flight unknowns. I expected squawks. I expected maintenance interruptions. I expected to revisit some test areas more than once. A task-based structure made those interruptions easier to absorb, because losing a week to a leak chase did not erase the logic of the program. It just paused the sequence.
What the program was trying to prove
The Phase 1 flights were organized around the familiar core ideas of experimental flight test:
- Basic controllability and safety of flight.
- Engine cooling, oil temperature, and pressure behavior during break-in.
- Stall behavior and approach-speed confidence.
- Airspeed accuracy.
- Climb-performance numbers.
- Configuration checks, pattern work, and operational confidence.
Those themes show up repeatedly in the N22UP flight log. The first flight focused heavily on break-in, temperatures, and safety. The June flights added early stall pulls and compression-check context. The July flights deepened the data set with airspeed calibration, repeated stall work, and climb testing. The point was not to chase a dramatic single “test pilot” moment. The point was to accumulate dependable answers.
The test cards mattered more than the calendar
The easiest way to think about this Phase 1 period is as a stack of test cards and spreadsheets that slowly turned into usable operating numbers.
Some flights were broad and exploratory. Others were narrow and repetitive:
- A local flight to watch cylinder head temperature trends.
- A short sequence to establish stall indications.
- A focused airspeed-calibration run.
- A cluster of climb-test flights to sort out Vx and Vy.
That rhythm is why the flying log looks uneven in places. There is a maintenance gap from June 19 to July 2. There are days with multiple short flights. There is a long airspeed-calibration day and a later cluster of climb-test flights. It was not random. Each of those flights was filling in a missing box.
The real deliverable was the operating-limits sheet
The most useful way to look back on this period is not as a diary of 35 flights and 40.45 hours, although those numbers matter. The real deliverable was the operating-limits worksheet for N22UP.
That sheet is where the scattered work becomes something permanent:
- White arc.
- Green arc.
- Maneuvering speed.
- Yellow arc.
- Vne.
- Supporting notes for the airplane’s operating envelope.
Every clean number on that page implies several earlier flights, some dead ends, some maintenance, and some judgment. The stall work feeds the low-speed side of the sheet. The airspeed calibration validates the instrument. The climb tests and general handling work help define how the airplane should actually be flown rather than merely how it can be flown.
Why this post belongs before the rest of the series
Without the framework, the later Phase 1 posts can feel disconnected. A leak chase looks like a random detour. A stall day looks like an isolated experiment. The airspeed work looks like number collecting for its own sake.
In reality, all of those stories belong to one program:
- Get the airplane safely airborne.
- Work through the early squawks without losing the thread.
- Build confidence in the airplane’s indications and behavior.
- Turn the results into operating numbers that mean something.
That is the lens I want on the rest of the Phase 1 write-up. The airplane did not just survive forty hours. It earned a documented envelope one answer at a time.
The next post in that sequence is Flights 2–5: The First Two Weeks, where the story moves from the excitement of first flight into the more revealing work of cooling tweaks, early stall checks, and the last flights before the airplane came apart for maintenance.