Materials index100% scale · Browser headers/footers off · 2 pages · Write on paper
Internal pilot · Drone basics simulatorv1.1 · 2026-10-20

One classroom copy · Instructor completes before class

Classroom and four-PC readiness checklist

Check date  Internal trial code  Owner code

Prepare the room

□ Desks, chairs and walkways clear □ No cable trip hazards □ Seating and screen distance checked
□ Paper and pens ready □ No physical aircraft or hardware link □ No-personal-data instruction given

Check all four PCs

Item · Mark ✓ / × / Not checked in each cellPC1PC2PC3PC4
Same local sim folder version / index.html opens    
Start screen, 3D and keyboard work offline    
Altitude hold (높이 유지 보조) on / Air movement (실내 공기 흔들림) off / Follow view (추적 시점)    
USB controller disconnected / keyboard-only input    
W/S, arrows, Shift and Space respond correctly    
P/Esc pause / Resume (계속하기) / Restart from beginning (처음부터 다시) checked    
Text, altitude and buttons readable / demonstration flight runs smoothly    

Check offline operation using an internally approved method. Do not alter network or security settings without authorization. If external font requests are blocked, confirm the local fallback font remains readable.

Start decision

□ All four PCs checked; start four-pair lesson □ Defer start: unchecked or unusable PC

Unchecked items and action required

If operation is interrupted

If any PC remains unavailable, the four-PC assumption no longer holds. Do not fail the affected learner. Switch to paper procedures/demonstration and reschedule missed individual observations. If running a reduced setup, record the actual PC count and changed practice allocation on the feedback sheet.

An actual eight-learner, four-PC concurrent lesson has not yet been validated. Blank fields are not test results. The instructor must complete checks on the actual PCs.
Internal practice · Real flight/FPV/USB not validated · No personal or classified unit information 1 / 2
Internal pilot · Drone basics simulatorv1.1 · 2026-10-20

One per PC · Keep USB validation separate

Per-PC input and device check record

PC □ 1 □ 2 □ 3 □ 4; browser/version

Edition version / PC number (exclude usernames and personal computer names)

Primary route: keyboard

  1. On the start screen, open PC check (PC 점검) → wait about 10 seconds. If needed, choose Measure screen speed again (화면 속도 다시 재기). Finishing this check alone does not establish classroom readiness.
  2. Choose a usable start-screen graphics setting: Normal (보통) / Light (가볍게) / Very light (아주 가볍게). Check readability and controls again after changing it.
  3. Start basic mission (기초 임무 시작) and check the three pre-flight items and P/Esc → Resume (계속하기). Test Space motor start and small W/S and arrow inputs.
  4. Check motor stop after landing at B and a fresh attempt. If the display stutters or input persists, defer classroom readiness.

Graphics chosen □ Normal (보통) □ Light (가볍게) □ Very light (아주 가볍게); displayed frame rate (optional)

□ Readable screen □ Keyboard only □ Pause/resume checked □ Hands-on input check done

USB controller · Not used in this core lesson

Current status: device not identified / practical validation pending
Menus and Gamepad API code do not prove a specific device's compatibility, axes, buttons, neutral position or reconnection behavior. This 120-minute plan and its internal judgments use keyboard input.

Use the section below only for a separate future validation. Do not connect devices spontaneously during class. Record a general model name only; do not collect serial numbers or personal PC names.

Future validation itemState
Device model/browser recognition / controller setup menu visible□ Not run □ Checked
Axis mapping, direction, neutral and mode settings / small virtual inputs□ Not run □ Checked
Return to neutral / pause / disconnect / reconnect□ Not run □ Checked
No simultaneous keyboard input / repeatable device behavior□ Not run □ Checked

Device model (optional)  Overall □ Not run □ More checks needed □ Checked

Issue and reproduction steps (no classified or personal information)

Do not mix USB and keyboard results to calculate improvement. This does not establish completed implementation or validation of FPV or real flight.