📘 Module 11 — Competition Strategy & Execution

11.1 Impound Checklist

Understanding the Impound Window and Its Constraints

Impound is the formal check-in process that occurs before competition begins — usually 30–60 minutes before the event window opens. During impound, teams are required to present their hovercraft vehicle and all associated materials to the event supervisor for inspection against the current-year rules. Once impounded, the vehicle remains under the supervision of the Science Olympiad organizing committee. Teams are not permitted to remove or modify the vehicle until the competition is complete.

This constraint is fundamental to Science Olympiad's integrity: it ensures that all teams compete with vehicles that were built during the designated preparation period (before the competition date), not hastily modified on-site. Missing the impound window disqualifies the team entirely from the event — there is no substitute, no exception, no second chance. Teams that arrive late do not compete.

The Allowed Materials Inventory

Science Olympiad rules specify exactly which materials teams may bring to impound and use during competition. For the Hovercraft event, the permitted inventory typically includes:

Vehicle and Propulsion:

• The hovercraft vehicle itself (only one)
• Motor (as specified in rules; often limited to a single electric motor)
• Battery (specifications vary by year; often a maximum size and chemistry are specified)
• Battery charging apparatus (if recharging between runs is allowed by rules)

Tools and Repair Materials (commonly permitted):

• Two class III calculators (required for score verification)
• Measuring tools: ruler, tape measure, calipers
• Fastening tools: screwdriver, wrench set, pliers
• Repair materials: duct tape, hot glue gun with glue sticks, spare skirt material, spare fasteners
• Lubricants: WD-40 or similar (for stuck parts, fan bearings)
• Replacement components: spare propeller, spare motor (if rules permit), spare battery (common)

Documentation:

• Engineering notes, design sketches, data sheets (commonly permitted as reference material)
• Previous test data and graphs (allowed as documentation; useful for strategy reference)

NOT Permitted (typical restrictions):

• Electronic aids beyond the two calculators (no phones, laptops, or tablets for timing or data)
• Power tools beyond hand tools (no electric drill, angle grinder, etc.)
• Materials not listed in the allowed inventory
• New components not explicitly declared at impound

The Pre-Impound Preparation Checklist

Teams should complete the following steps in the 24 hours before impound:

Vehicle Assembly & Function Test:

• [ ] Assemble the complete hovercraft and verify all parts are secure
• [ ] Test the motor: switch on, verify rotation direction, check that fan produces audible thrust
• [ ] Test the battery: measure voltage with a multimeter; should read nominal value (e.g., 7.4V for 2S LiPo) or greater
• [ ] Perform a static lift test: with motor running, listen for the characteristic air hiss and feel for upward lift force by pressing down gently on the hull; the craft should resist downward pressure
• [ ] Walk through a full run: place the craft on the floor, activate the motor, release, and observe that it translates forward smoothly for at least 1 meter without veering excessively

Physical Inspection:

• [ ] Inspect the skirt for tears, thin spots, or wrinkles; repair any damage with heat-sealed patches
• [ ] Check all fasteners (bolts, screws, tape joints) for tightness; apply threadlocker to any loose bolts
• [ ] Verify the propeller is straight and not bent; spin it by hand to check for wobble
• [ ] Inspect the hull bottom for warping, cracks, or sharp edges; sand any sharp edges smooth
• [ ] Ensure wiring is secured and not pinched by moving parts

Battery and Power System:

• [ ] Charge the battery to full capacity; measure the resting voltage
• [ ] If bringing a second battery, charge it as well
• [ ] Verify all connectors are clean and make good electrical contact
• [ ] If using a battery balance charger, check all cell voltages; they should be within 0.1V of each other

Tools and Materials Inventory:

• [ ] Pack all allowed tools into a clearly labeled bag; make an itemized list
• [ ] Verify that the two class III calculators are present and functional
• [ ] Confirm that all materials are in the impound bag: spare skirt material, tape, glue sticks, spare fasteners
• [ ] Check that documentation is organized: test data, design notes, previous graphs

Rules Compliance:

• [ ] Review the current-year rules one final time, checking all constraints: motor specifications, battery size/weight limits, maximum dimensions, construction material restrictions
• [ ] Verify that your craft complies with all specified constraints; measure dimensions if necessary
• [ ] Ensure no prohibited materials are present

The Impound Presentation

During the impound window, teams typically submit to the following sequence:

1. Registration and Rules Check: Event supervisor reviews the team number, division, and school. An initial visual inspection is performed to ensure the vehicle looks complete and plausible.

2. Static Inspection: The supervisor examines the vehicle for:

   • Structural integrity (no obvious damage or loose parts)
   • Compliance with material and construction rules (e.g., no prohibited glues, no motor types outside spec)
   • Overall dimensions against any specified size limits

3. Functional Inspection: The supervisor may request:

   • A static motor test (switching on to verify the fan runs)
   • A demonstration run (usually on a practice track adjacent to competition)
   • Documentation review (confirming design notes are present)

4. Inventory and Sealing: Approved tools and materials are logged. In some tournaments, the impound bag is sealed with tape and labeled. The vehicle itself may be marked with a label. The team receives a receipt with the inventory list.

5. Escort to Holding Area: The vehicle and materials are transported to the impound holding area where they remain under supervision until the event window.

Last-Minute Impound Adjustments

If, during the impound functional test, the vehicle fails to hover or demonstrates a critical malfunction, teams usually have a brief window (5–15 minutes) to make repairs using only hand tools and materials already in the impound bag. Common quick fixes:

• Skirt re-sealing: Hot glue a small tear or reseal a leaking seam
• Fan realignment: Loosen and reseat a fan mount that has shifted during transport
• Propeller replacement: If the spare is allowed and documented, swap a bent propeller for a straight one
• Loose fastener tightening: Quick wrench adjustment of bolts

However, major structural changes (e.g., replacing the entire skirt, rebuilding a motor mount, or swapping the motor itself) are typically not allowed during the impound period. This underscores the importance of thorough pre-impound testing — arriving at competition with a known-working vehicle is critical.

Competition Tip: Arrive Early and Stay Organized

Teams should arrive at the competition venue at least 30 minutes before the impound window closes. Impound windows are strict — if impound closes at 10:00 AM and your team arrives at 10:05 AM, you are disqualified. Unexpected traffic, registration delays, or last-minute questions can consume time.

Organize your impound bag with clear labels and a printed inventory. If the supervisor asks, "Do you have spare tape?" and you can immediately point to it, it demonstrates professional preparation. More importantly, an organized bag prevents you from accidentally leaving behind critical repair materials.

11.2 Pre-Run Inspection & Setup

The Pre-Run Sequence: A Scripted Routine

Once the event window begins, teams transition from the impound holding area to the competition floor. They have 8 minutes total to complete setup, inspection, and all run attempts. This tight time budget demands a scripted pre-run inspection routine that each team practices and executes identically across all attempts. The routine must be fast (~90 seconds) while catching the most likely failure modes.

Teams that have rehearsed their inspection sequence can execute it reflexively under pressure, freeing mental resources for tactical decisions (should we accept this run score or attempt another?) rather than procedural fumbling.

The Pre-Run Checklist (90-Second Sequence)

Teams should time-practice this sequence repeatedly during training:

Step 1: Visual Hull Inspection (15 seconds)

• Place the craft on a flat work surface
• Inspect the hull bottom under good lighting (bring a flashlight if needed) for cracks, warping, or new damage
• Check that tape joints are secure and not peeling
• Verify no debris is stuck to the hull bottom (lint, tape remnants)

Step 2: Skirt Integrity Check (20 seconds)

• Visually inspect the skirt for new tears, punctures, or loose seams
• Gently flex the skirt material near the hull attachment to ensure it is still sealed
• Check the seam at the skirt base where it attaches to the hull; look for air leakage evidence (dust or lint being drawn toward the seam)
• If a tear is visible, deploy the repair kit: hot-glue a tape patch over the hole

Step 3: Motor and Fastener Check (15 seconds)

• Visually inspect the fan mount: look for any movement or loose bolts
• Check the motor wire connection: confirm the connector is seated and not loose
• Verify the propeller is straight (spin it by hand; it should not wobble)

Step 4: Battery & Electrical (15 seconds)

• Check the battery voltage with a multimeter if time permits; it should read ≥90% of nominal (e.g., ≥6.7V for a 7.4V 2S pack)
• Verify the battery connector is secure
• Confirm the on/off switch or speed controller is accessible and functional

Step 5: Positioning and Launch Prep (15 seconds)

• Move the craft to the launch line, aligning it precisely with the reference mark on the hull against the tape mark on the floor
• Ensure the craft is level and not tilted to one side
• Clear the runway of any debris within 3 meters
• Verify that the data recording operator is ready with stopwatch and clipboard

Step 6: Pre-Launch Checklist Verbal Confirmation (5 seconds)

• Operator: "Ready to launch?"
• Data operator: "Timer ready, distance markers visible, data sheet prepared."
• Operator: "Launching in 3, 2, 1..."

Addressing Common Pre-Run Issues

Issue: Skirt has a small tear (~1 cm) Quick fix: Apply hot glue to the tear and press a small piece of duct tape over it. Cure time ~30 seconds. This should hold for at least 1–2 more runs.

Issue: Battery voltage is low (~80% of nominal after just one run) This indicates a possible battery problem or excessive current draw. Options:

• Switch to the backup battery (if impound rules allow and you have one)
• Check the motor wiring for a short circuit (gently wiggle the wire near the connector; motor current draw should not spike)
• Reduce fan speed setting for the next run (trade speed for battery conservation)

Issue: Motor doesn't spin or spins sluggishly Quick diagnostics:

• Check that the propeller is not jammed by a piece of tape or debris
• Verify that the switch or speed controller is actually on
• Confirm that the battery is connected and charged
• If the motor still doesn't spin, the craft is likely disabled for that run

Issue: Craft won't hover; drags on the floor This is the most serious pre-run issue. Possible causes and diagnostics:

• Insufficient fan speed: Increase the speed setting (if adjustable) and test again
• Skirt leak: Look for air escaping from seams or pinholes. Deploy repair tape if found.
• Flat battery: Measure voltage; if <85% of nominal, swap to backup battery or accept that run time will be slow
• Motor failure: If the motor is running but producing low thrust, there may be an internal issue; move to backup motor if available

If the craft still will not hover after these checks, the run is effectively failed. The team must decide: accept the score (likely zero or very low) or use one of their remaining attempts to try again after further repair.

The Role of the Second Team Member

With only two participants allowed, role division is critical:

Primary Operator:

• Physically launches and controls the craft
• Performs the inspection sequence
• Makes real-time decisions about run acceptance

Data Operator & Timekeeper:

• Manages the stopwatch (starts and stops timing based on visual cues)
• Records run time and distance immediately after each run
• Fills in the data sheet with run number, time, distance, and notes
• Monitors the 8-minute timer for the entire event
• Alerts the operator to time remaining ("2 minutes left; this is likely your last run")

During the inspection sequence, the data operator can assist with the pre-run checks (holding the flashlight for skirt inspection, spotting debris, etc.) but must remain ready to transition immediately to data recording once the launch begins.

Competition Tip: The "Standardized Setup" Edge

Teams that have practiced their inspection sequence to the point where it becomes reflexive gain a psychological advantage: they perform it identically in the low-stress practice environment and under high-pressure competition conditions. There are no surprises, no fumbling, no forgotten steps. Meanwhile, teams that don't rehearse systematically often discover, at competition, that their inspection sequence doesn't fit in their time budget, or that they've forgotten to check something critical.

The inspection routine is not a bureaucratic overhead — it is an engineering quality-assurance process. Teams that treat it seriously improve their consistency and reliability, which directly correlates with higher scores.

11.3 Reading the Track

Why Track Reconnaissance Matters

The competition floor surface that you will test your hovercraft on is not identical to the surfaces used during practice. Even if you practiced on a gymnasium floor that looks identical to the competition venue, there are subtle differences that affect hovercraft performance:

• Floor finish: Polished vs. matte; waxed vs. unsealed; age and wear patterns
• Surface micro-texture: Gym floor grain direction; concrete smoothness; tile grout lines
• Temperature: Cooler surfaces may affect skirt material stiffness and battery discharge rate
• Humidity: Affects air density, which affects lift pressure and drag
• Ambient air currents: HVAC systems, open doors, or ventilation patterns create subtle drafts

These factors shift the baseline performance of your craft slightly relative to your practice data. A team that acknowledges this variation and adjusts can compensate. A team that ignores it may be surprised by slower-than-expected times or unexpected steering drift.

The Track Walk-Through: Conducting a Physical Inspection

Before your first official run attempt, if rules permit, conduct a practice run on the competition floor. If a practice run is not permitted, spend 5 minutes physically walking the track and taking notes:

Step 1: Surface Texture Mapping (2 minutes)

• Walk the length of the track slowly, observing the floor closely
• Identify any joints, seams, or surface discontinuities (common on gymnasium floors where separate floor sections meet)
• Note any change in finish (e.g., "polished oak from 0–10 m, matte painted tile from 10–15 m")
• Check for debris accumulation in corners or along the edges
• Feel the floor surface: is it slick or slightly grippy to your shoe?

Step 2: Environmental Observation (1 minute)

• Stand at one end of the track and feel for air movement (open doors, HVAC outlets)
• Note the lighting direction; if sunlight comes through a window, it may create a glare zone that affects operator vision
• Check the ambient temperature; if it is significantly warmer or cooler than practice, note it

Step 3: Track Layout and Boundaries (1 minute)

• Identify the launch line and the target zone (e.g., "must reach 3.0 m")
• Note any physical barriers or boundaries that would stop the craft (walls, markings, obstacles)
• Verify that distance markers or cones are in place and clearly visible

Step 4: Comparison to Practice Data (1 minute)

• Mentally compare the track surface to your practice venue
• If the track is significantly more grippy, expect slower run times and consider increasing fan speed
• If the track is more slick, expect faster times and consider reducing fan speed to maintain better control

Using Practice Data to Predict Competition Performance

Onceyou have assessed the competition floor, use your practice data to make a surface-correction prediction:

From your practice testing, you have characterized your craft's speed as a function of fan setting. For example: "At 65% fan speed on a gymnasium floor, we achieve 3.8 s run time for 2.5 m (speed ≈ 66 cm/s)."

If the competition floor appears slightly more grippy (higher friction coefficient μ), you can estimate the performance change:

Approximate friction-based time adjustment: T_comp ≈ T_practice × √(μ_comp / μ_practice)

For a 10% increase in surface friction (μ_comp = 1.1 × μ_practice): T_comp ≈ 3.8 × √(1.1) ≈ 3.8 × 1.049 ≈ 3.99 s

So you'd expect approximately 4.0 s instead of 3.8 s — a 0.2 s increase. If your scoring function penalizes time heavily, you should consider bumping fan speed from 65% to 70% to recover some speed.

This is an estimate, not exact, but it provides a rational basis for your first-run fan setting rather than guessing.

Common Track Variations and Their Physical Causes

Gymnasium hardwood floor with grain direction Wood floor grain creates subtle directionality in friction. Running parallel to the grain is slightly different from running perpendicular. If you notice directional drift during your practice run, it may be grain-induced. Adjust your starting position or verify that your craft's steering is as neutral as possible.

Concrete floor with seams/control joints Large concrete floors contain expansion joints (typically every 10–15 m) to prevent cracking. These appear as raised seams ~5–10 mm tall. If your hovercraft encounters a seam at speed, it may produce a small bounce or stutter. This is usually not catastrophic, but if your craft is very low-riding (marginal hover height), seams could cause brief floor contact. If you observe seams on the competition floor, make a note of their location and mentally prepare for possible artifacts when crossing them.

Tile floor with grout lines Polished tile floors for large spaces are usually laid with distinct grout lines between tiles. These are typically 3–5 mm wide. At low hovercraft speeds (<1 m/s), grout lines may create drag as the skirt edge catches momentarily on the grout. This is usually negligible, but it can add 1–2 cm of random jitter to final stopping distance. If the competition floor has visible grout lines, expect stopping distances to vary by ±2 cm due to the randomness of which grout line your craft aligns with.

The First Run as a Calibration Test

Your first official run is not just a competition attempt — it is a calibration test. Treat it as:

• Launch at the fan speed that your practice data suggests
• Record time and distance carefully
• Observe the craft's behavior: is it faster or slower than expected? Does it steer true or drift?
• After the run, compare the result to your prediction
• Use the difference to adjust fan speed for subsequent runs

If your prediction was 3.8 s but you measured 3.5 s, the floor is slicker than your practice venue. You could increase fan speed for the next run if you want to push distance. If your prediction was 3.8 s but you measured 4.2 s, the floor is grippier — reduce fan speed if you were trying to run too fast and sacrificing control.

Competition Tip: Document Track Notes Immediately

During your track walk-through, write down specific observations in your notebook: "Floor is matte polished oak, slightly grippy. No visible debris. HVAC vent near south wall creates ~0.5 m/s crosswind. Predicted performance: +2% time penalty vs. practice." These notes guide your first-run strategy and provide a reference point if you need to troubleshoot mid-competition.

11.4 Run Decision Making

The Strategic Structure of Multiple Attempts

Unlike a written test where a team takes it once and lives with the result, the Hovercraft event structure typically allows multiple run attempts within the 8-minute event window. Depending on the exact rules and scoring formula, teams may be allowed 2–5 attempts, with scores calculated as either the best single run or the average of all runs.

This structure creates a strategic problem: when should you accept a run score, and when should you forfeit it and attempt again? The answer depends on:

• How many attempts you have remaining
• Your current best score
• Your confidence in improving on the next run
• The uncertainty in your craft's performance

The Optimal Stopping Rule

This is a classic problem in decision theory: the secretary problem or optimal stopping. In its simplest form:

If you have N total attempts remaining, accept the current run if its score exceeds the expected value of future runs.

Formal analysis: Let S_current be the score of the current run, and E[S_future] be the expected value of your best score if you use one more attempt. Accept if:

S_current > E[S_future]

The challenge is estimating E[S_future]. It depends on:

• Your craft's variability (CV from practice testing)
• Your current best score to date (in your competition session)
• How many attempts remain

Practical Implementation: The Heuristic Approach

In competition, you don't have time for formal Bayesian analysis. Instead, use this heuristic:

Rule 1: Always accept the first run if it is in the "normal" range for your craft From practice testing, you know your typical run time and distance. If your first run falls within ±1 standard deviation of your mean (i.e., not an outlier, either exceptionally good or bad), accept it. Reason: using a second attempt risks a worse result for minimal upside.

Rule 2: Reject if the current run is clearly worse than your recent practice average If you measured 4.2 s in competition but practice typically produces 3.8 ± 0.3 s, this run is an outlier (>1 σ worse). Reject it and try again. You likely have at least one more attempt in your time budget.

Rule 3: Accept if you have only one attempt remaining Once you reach "this is the last attempt" due to time constraints, accept whatever score you achieve. Attempting again would forfeit the entire event.

Rule 4: Reject outstanding runs only if you are certain you can beat it If you achieve an exceptional run (>1 σ better than your practice mean) and you have 1–2 attempts remaining, the decision is harder. If your craft's variability is low (CV < 10%) and you feel confident about repeating that run, attempt again. If your craft is highly variable (CV > 20%), accept the outlier high result rather than gambling that the next run will also be exceptional.

Quantitative Decision Framework

For teams with strong data from practice testing, here is a more explicit framework:

Let:

• S_best_session = your best score so far in the current event
• S_current = the score of the run you just completed
• σ_craft = the standard deviation of your craft's performance (from practice)
• n_remaining = number of attempts remaining in the 8-minute window

Calculate the improvement probability: P_improve = Pr(S_next > S_current)

For a normal distribution with your craft's estimated mean μ and standard deviation σ: P_improve = 1 − Φ((S_current − μ) / σ)

where Φ is the cumulative normal distribution.

Rough guideline:

• If P_improve < 30%, accept (less than 1-in-3 chance of improvement; not worth the risk)
• If P_improve > 50%, reject (better than even odds of improvement; worth the attempt)
• If 30% < P_improve < 50%, marginal (use Rule 1–3 above for tie-breaking)

The Time Constraint and Run Pacing

The 8-minute total time budget includes setup (90 s), inspection (60–90 s), and runs. Each run consumes:

• Launch and execution (~10 s)
• Data recording and inspection (~30 s)
• Setup for next run (~30 s)

Total per run: ~70–90 seconds. This means 8 minutes permits approximately 5–6 complete run cycles, with some margin for troubleshooting or quick repairs.

Time-based pacing strategy:

• At 4 minutes elapsed: you should have completed at least 2 runs. Decide if you are satisfied or will attempt a third.
• At 6 minutes elapsed: you should have completed at least 3 runs. This is your last opportunity to attempt another run; if you attempt now, it will be your final run.
• At 7:30 elapsed: stop all attempts and prepare for final submission.

This pacing prevents you from running out of time with unresolved attempts or partial data.

Case Studies: Decision-Making in Context

Scenario 1: Outlier Low Run Your practice data: mean = 3.8 s, σ = 0.25 s. First competition run: 4.5 s (distance 2.2 m, score 12.0). Observation: This is approximately 3 σ worse than your mean — a clear outlier. Decision: Reject. The run time is far outside your expected range, suggesting a mechanical issue (possible skirt leak, low battery) that should be investigated before the next run. Use the rejection to inspect the craft and correct the issue.

Scenario 2: Solid Run, But Feeling Confident Your practice data: mean = 3.8 s, σ = 0.40 s, CV = 10%. First competition run: 3.8 s (distance 2.5 m, score 15.5). Observation: Exactly on your mean — a baseline result. You feel confident about repeating it or doing better. Time consumed: 2 minutes. Time remaining: 6 minutes (room for 3–4 more attempts). Decision: Reject and try again. You have ample time, and a CV of 10% indicates your craft is repeatable. There is >40% probability the next run will match or exceed this one.

Scenario 3: Excellent Run, Limited Time Remaining Your practice data: mean = 3.8 s, σ = 0.35 s. Run achieved at 6:30 elapsed: 3.2 s (distance 3.0 m, score 22.0). Observation: This is approximately 1.7 σ better than your mean — an excellent result. Time remaining: 90 seconds (room for ~1 more attempt). Decision: Accept. This is too good to risk. Even if the next run is excellent, the probability that it exceeds 3.2 s is <50%. With only one attempt slot remaining and a strong score in hand, the rational choice is to preserve this result.

Competition Tip: Pre-Plan Your Decision Criteria

Before competition, discuss with your teammate and write down your stopping rules. For example:

"Our stopping rule for this competition:

• Rule 1: Accept first run if 3.5 < T < 4.2 seconds
• Rule 2: Reject if T > 4.5 s (something is wrong; investigate)
• Rule 3: With 2+ attempts remaining, reject if current score is within practice mean ± 0.5 s
• Rule 4: Always preserve the best run; do not attempt after 6:30 elapsed"

Writing this down in advance prevents debate under pressure. When a run completes, you reference the pre-written criteria, make a decision, and move on.

11.5 Time Management During the Event

The 8-Minute Envelope: Compartmentalizing the Event Window

The entire hovercraft competition window — from the moment your team enters the competition floor to the moment your last run completes — is constrained to 8 minutes total. This is approximately the time it takes to watch a single scene of a television show. Within this window, you must:

1. Set up the craft and materials
2. Perform the pre-run inspection
3. Execute 2–5 run attempts
4. Record timing and distance for each run
5. Make strategic decisions about which runs to accept or forfeit
6. Troubleshoot any mechanical issues that arise
7. Pack materials for submission

No extensions are granted. If your team is still attempting runs at 8:00.5, the event ends and your best completed run is your score. Time management is not ancillary — it is a core competition skill that directly determines which runs you are able to complete.

The Time Budget Breakdown

Here is a realistic allocation for the 8-minute window:

This budget assumes smooth execution. Any troubleshooting (skirt repair, battery swap, loose fastener fix) consumes an additional 60–120 seconds, typically forcing the team to abandon one planned run.

Tactical Time Management: The Three Checkpoints

Teams should track elapsed time against these checkpoints:

Checkpoint 1: 2-Minute Mark

• Should have completed: First inspection and Run 1
• Status check: Is the craft working? Did you achieve a baseline score?
• Decision point: If Run 1 failed or was extremely slow, diagnose the issue now. If Run 1 was nominal, proceed to Run 2.
• If behind: You have 6 minutes for 3–4 more runs. Manageable.
• If ahead: You have built time buffer for troubleshooting later. Proceed confidently.

Checkpoint 2: 4:30 Mark

• Should have completed: Run 2 and preliminary decision (Run 3 or not?)
• Status check: Do you have a good score? What is your best run so far?
• Decision point: If your best score is strong and time is tight, prepare to make 4:30 your last run. If your best is weak or you have time buffer, commit to one more attempt.
• If behind: You have 3:30 remaining. This permits only 1–2 more runs. Be selective about running again.
• If ahead: You have 3:30 for potentially 2–3 more runs. Use it strategically.

Checkpoint 3: 6:30 Mark

• Should have completed: At least 3 runs, with a final decision on whether to attempt again
• Status check: This is effectively your "last call for attempts"
• Decision point: If you attempt a run now, it will be your final run with only ~1.5 minutes for one more attempt after it completes.
• If behind: 1:30 remains. Sufficient for one more run if you hurry, but minimal margin for error.
• If ahead: You have potential for one final run at 7:00. Proceed only if you believe the benefit justifies the risk.

Hard Stop: 7:45

• All attempts must be completed by 7:45 to allow data submission and score calculation before 8:00.

Preventing Time Bleed: The Operator's Role

The data operator has a critical time-management responsibility: maintaining awareness of elapsed time and communicating it to the primary operator.

Suggested pacing announcements:

• "2 minutes elapsed. Making good time."
• "4 minutes elapsed. This is your last attempt if you want two more runs."
• "6 minutes elapsed. Next run must be your last."
• "7:30 elapsed. Stop all attempts. We need to finalize data."

Without this time-awareness communication, the primary operator focuses entirely on the craft and can lose track of elapsed time, resulting in a scramble at the end.

Contingency Time Management: Troubleshooting Under Pressure

Despite excellent preparation, issues sometimes arise:

Issue: Skirt develops a tear during Run 1 (occurs at 1:30) Response:

• Abort Run 1 (do not waste time completing it if it is failing)
• Spend 60 s repairing the skirt (hot glue + tape)
• Resume with Run 2 at ~2:40
• Revised checkpoint: You now have only 4 remaining runs planned, but the repair consumed 1:10. Adjust remaining attempts downward (now plan for 2–3 more runs instead of 3–4)

Issue: Battery is depleted after Run 2 (occurs at 2:45) Response:

• Swap to backup battery (30 s, assuming it is in the impound bag and charged)
• Measure new battery voltage (15 s)
• Resume at ~3:30
• Revised checkpoint: You have 4:30 remaining, sufficient for 2 more attempts

Issue: Craft drifts dramatically off-course during Run 3 (occurs at 4:00) Response:

• Use the post-run inspection (normally 30 s) to diagnose the drift
• Likely causes: warped propeller, loose fan mount, or off-center weight distribution
• Quick fix options:
  • Propeller swap: 45 s
  • Fan mount re-tightening: 20 s
  • Weight balance check: 15 s
• If drift is fixed quickly: you lose 30–45 s but can resume for Run 4 at ~4:30
• If drift is not quick to fix: accept that you will have only 1 more attempt remaining (Run 4), then stop

Scheduling Strategy: Conservative vs. Aggressive

Conservative Approach (best for low-variability, reliable craft):

• Complete 3 runs and stop
• Allocate time: Run 1 at 2:00, Run 2 at 3:15, Run 3 at 4:30, stop
• Rationale: With a reliable craft, 3 data points give a robust average. Avoids risk of a late-attempt failure
• Best case: all 3 runs succeed and you have a strong average score
• Worst case: you have 3 runs completed; even if one is mediocre, two good runs remain

Aggressive Approach (best for high-variability, potentially high-performance craft):

• Attempt 4–5 runs, accepting only the best
• Allocate time: Run 1 at 1:45, Run 2 at 2:50, Run 3 at 4:00, Run 4 at 5:15, Run 5 at 6:30 (if time permits)
• Rationale: With multiple attempts, you can cherry-pick the best run. Variability works in your favor.
• Best case: you hit an outstanding run (outlier high) late in the session; it becomes your score
• Worst case: you run out of time and have to submit based on whatever your last completed run was

Balanced Approach (recommended for most teams):

• Target 3–4 runs, with optional 5th run depending on how well the first 3 go
• Allocate time: Run 1 at 2:00, Run 2 at 3:10, Run 3 at 4:30, Run 4 at 6:00 (optional)
• Rationale: Provides two solid data points, flexibility to attempt a third, and potential for a fourth if going well

Competition Tip: Practice the Full Event Sequence Under Time Pressure

In the weeks before competition, conduct at least two full-event simulation sessions at your practice facility. Set a timer for 8 minutes and run through the complete sequence: setup, inspection, three full runs, decision-making, data recording, all under the time constraint. This reveals:

• Whether your inspection sequence actually fits in 90 seconds or requires 120 s
• How long a typical run cycle really takes with your specific craft and measurement method
• Where time bleeds occur (is data recording slower than you estimated?)
• Whether your team's rhythm and communication are smooth or chaotic under time pressure

Teams that have done this simulation multiple times arrive at competition with a realistic time plan and the confidence to execute it.

11.6 Communicating as a Two-Person Team

The Division of Labor Imperative

The Hovercraft event allows only two participants on the competition floor at once. This is not a limitation to work around — it is a feature that, properly managed, forces team efficiency and clarity. Two people can accomplish more in 8 minutes when roles are crystal clear than three people can when duties overlap and communication is ambiguous.

The tight 8-minute window leaves no time for confusion about who does what. Teams that have practiced their role assignments and communication protocols gain a measurable time advantage over teams that figure it out on the fly.

Role Definition: The Operator and the Data Manager

Primary Role: Craft Operator

• Responsibility: Physical manipulation of the hovercraft and execution of runs
• Before run: Perform the inspection sequence, position the craft at the launch line, ensure the track is clear
• During run: Activate the motor, release the craft, observe its trajectory and performance
• After run: Retrieve the craft from the end of the run and return it to the work station
• Decision making: Make the call on whether to accept or reject the run score (in consultation with the data manager)

Secondary Role: Data Manager & Timekeeper

• Responsibility: Timekeeping, distance measurement, data recording, and strategic timing of the 8-minute window
• Before run: Prepare the stopwatch, position distance markers, ready the data recording sheet, confirm the operator is prepared
• During run: Activate stopwatch at the signal (typically when the craft first moves), stop timing when the craft comes to rest, identify distance landmarks
• After run: Measure or record the final distance, record time and distance on the data sheet, announce elapsed time to the operator, guide pacing decisions
• Strategic role: Maintain awareness of the overall time budget and alert the operator to time remaining for the next run

Communication Protocol: Essential Signals and Phrases

Verbose communication slows everything down. Teams should establish standardized signals and brief phrases that are used consistently:

Pre-Run Checklist (Operator → Data Manager):

• Operator: "Ready for [Run X]?"
• Data Manager: "Distance markers set, stopwatch ready, data sheet prepped. Go."
• Operator: "Launching in 3, 2, 1, launch."

During Run:

• Data Manager: [Visually tracks the craft's trajectory]
• Data Manager: (Immediately upon craft stopping) "Stop." [Stops stopwatch]

Post-Run Data Collection (typically 20–30 seconds):

• Data Manager: "Time was [X] seconds. Measuring distance..."
• Data Manager walks to where the craft stopped, places a measuring tape from the launch line to the craft's resting position
• Data Manager: "Distance: [X] centimeters. Recording." [Writes data]
• Data Manager: "Run [X] complete: [time], [distance]. Elapsed time: [total]."

Run Decision (Operator & Data Manager):

• Data Manager: "Last run was [time] seconds, [distance] meters. That's [score] points. Better or worse than [previous best]?"
• Operator: (After ~10 seconds thought) "Accept / Reject."
• Data Manager: "Understood. [Setup for next run / Preparing final submission]."

Time Announcements (Data Manager → Operator, at key checkpoints):

• "2-minute mark. We're on pace."
• "4 minutes elapsed. Last chance for a third attempt."
• "6 minutes elapsed. Next run will likely be your last."
• "7:30. We're done attempting. Finalizing data."

Avoiding Communication Traps

Trap 1: Simultaneous Decisions Operator and Data Manager independently deciding whether to accept or reject a run creates conflict. Instead: Data Manager presents the factual result ("Score is 16.5 points, better than our previous 14.2"), and Operator makes the strategic call ("Let's attempt one more run"). One decision-maker per decision.

Trap 2: Ambient Conversation Drowning Out Critical Information Informal chatting between runs can obscure important signals ("Did you say 6 minutes elapsed?"). Establish a rule: post-run interval is for data recording and pacing announcements only. Informal discussion can occur before the event window starts.

Trap 3: Operator Distracted by Timing Details The operator should focus entirely on launching and observing the craft. The data manager owns all timing and scoring details. Operator should not be checking their watch or calculating scores; that's the data manager's domain.

Trap 4: Data Manager Missing Critical Observations While recording data, the data manager should also be observing the craft's behavior ("It drifted left on that run"). If something looks unusual, the data manager should flag it: "Did you notice the craft veered left? Check the propeller angle before the next attempt." This kind of real-time observation can prevent failures on the next run.

Handling Disagreement: Pre-Planned Tiebreaker

Occasionally, operator and data manager may disagree on strategy:

Scenario: After Run 2, Operator wants to stop and submit the best score so far. Data Manager argues there is time and battery for one more attempt.

Resolution: Pre-decide who has final authority. Common approaches:

• Operator authority: The operator, who knows the craft's handling, has final say
• Data manager authority: The data manager, who owns the strategic time budget, has final say
• Consensus rule: Disagreement → accept the run and don't attempt again (defaults to conservative strategy)

Write down your tiebreaker rule before competition. When disagreement arises under pressure, reference the rule and move on without debate.

Managing Nerves: The Psychological Dimension

In the 8-minute window, stress levels are high. Communication can deteriorate into short, clipped replies or even silence if teams are nervous. Counteract this:

Before competition, practice calming phrases:

• Data Manager: "We're doing great. Right on pace." (Even if things are slightly behind, reframing as control-focused rather than panic-focused helps)
• Operator: "Solid run. Let's review our options." (Treating each run as data, not as success/failure)

Establish a post-run ritual:

• After each run completes, take 5 seconds for a deliberate pause — breathe, acknowledge the result, then proceed to the next task. This prevents cascade failures where nerves from one run bleed into the next.

Normalize technical issues:

• If the craft fails to hover or exhibits a problem, the data manager should respond matter-of-factly: "Skirt pressure seems low. Let's check for leaks." Treating issues as solvable engineering problems, not as disasters, keeps morale stable.

The Communication Advantage: Why It Matters

Teams with clear communication protocols and practiced role division typically complete their event 60–90 seconds faster than teams without them. This time savings translates directly into one additional full run attempt, or to a final inspection before submission, or to a buffer against unexpected delays.

In a sport where placement often hinges on fractional differences in score, gaining access to one additional run or a few seconds of buffer time is significant. Communication efficiency is a legitimate competitive advantage.

Competition Tip: Conduct a Team Debrief After Each Practice Session

After every full-length practice session (especially the timed 8-minute simulations described in Topic 11.5), spend 5 minutes debriefing as a team:

• "What communication breakdowns occurred?" (E.g., "You measured distance but I didn't hear the result clearly")
• "What slowed us down most?" (E.g., "The data recording took 45 seconds because we weren't sure of the exact distance")
• "What went smoothly?" (E.g., "The pre-run inspection took exactly 90 seconds as planned")
• "What should we adjust for next time?" (E.g., "Let's use a laser distance meter instead of a tape measure to speed up measurement")

This continuous improvement of communication and procedure — tested under time pressure — is how elite Science Olympiad teams achieve their edge.