Helicopter Landing Zone Setup Checklist
Helicopter Landing Zone Setup Checklist template for verifying a safe non-helipad landing area before aircraft arrival. Use it to control hazards, confirm visibility, and document go/no-go readiness.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Emergency Medical Services · Public Safety · Construction · Wildland Fire · Healthcare
Overview
This Helicopter Landing Zone Setup Checklist template is for inspecting and documenting a temporary landing area before a helicopter arrives at a non-helipad scene. It walks the user through scene control, landing zone selection, hazard mitigation, lighting and visibility, communications, and final go/no-go readiness.
Use it when a helicopter needs to land at an incident scene, remote work area, disaster site, or other improvised location where the landing zone must be created and verified in real time. The checklist helps the coordinator confirm that the area is large enough, the surface is stable, approach and departure paths are clear, loose objects are secured, and the crew has the information needed to land safely.
Do not use it as a substitute for the aircraft operator’s procedures, local emergency response protocols, or site-specific aviation guidance. It is also not the right tool for a permanent helipad inspection, aircraft maintenance check, or flight operations log. If the scene has active overhead wires, uncontrolled debris, poor visibility, or unresolved communications gaps, the correct outcome may be no-go until the deficiency is corrected. The template is designed to make that decision visible, defensible, and easy to hand off.
Standards & compliance context
- This template supports emergency scene control practices commonly used under OSHA general industry and construction safety expectations, especially where workers are exposed to moving equipment, struck-by hazards, and site hazards.
- The hazard and perimeter controls align with standard incident-command and aviation safety practices used by EMS, public safety, and the Authority Having Jurisdiction.
- Lighting, visibility, and ground-person briefing items reflect common helicopter landing zone guidance used by aircraft operators and emergency response agencies.
- If the scene involves fuel, flammables, or ignition sources, the checklist helps document controls consistent with fire-safety and hazardous-area precautions recognized by NFPA-based programs.
- For healthcare or EMS transport operations, the template can support local medical transport policies without replacing the aircraft crew’s own landing requirements.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Scene Control and Landing Zone Selection
This section matters because the safest landing zone starts with the right location, a stable surface, and a controlled perimeter before any other hazard work begins.
-
Landing zone diameter is at least 100 feet and clearly defined
Confirm the usable landing area is a minimum of 100 feet in diameter, or larger if aircraft/operator guidance requires it.
-
Landing zone surface is level, firm, and free of loose debris
Check for ruts, soft ground, standing water, loose gravel, trash, tools, or other material that could be blown by rotor wash.
-
Approach and departure paths are unobstructed
Verify there are no trees, poles, wires, antennas, vehicles, structures, or other obstructions in the intended approach/departure paths.
-
Landing zone perimeter is established and controlled
Confirm the perimeter is marked and kept clear of bystanders, nonessential personnel, and unsecured equipment.
Hazard Identification and Mitigation
This section matters because rotor wash and low-altitude flight make wires, loose objects, fuel, and ignition sources immediate threats that must be controlled or removed.
-
Overhead utility lines and poles identified and avoided
Confirm all overhead hazards are identified, communicated to the pilot/aircrew, and outside the landing and approach area.
-
Loose objects secured against rotor wash
Secure tarps, paper, lightweight equipment, signage, cones, and other items that could become airborne.
-
Fuel, flammables, and ignition sources are removed or controlled
Verify fuel cans, oxygen cylinders, smoking materials, open flames, and other ignition sources are kept away from the landing zone.
-
Scene hazards are documented and communicated to the aircraft crew
Confirm known hazards such as wires, terrain slope, dust, snow, smoke, or nearby traffic are relayed to the pilot or air medical crew.
Lighting and Visibility
This section matters because the pilot must be able to see the zone, judge depth and boundaries, and avoid glare or obscured conditions during approach and departure.
-
Landing zone is adequately illuminated for current conditions
Confirm lighting provides clear visibility of the landing area, perimeter, and hazards without creating glare or blinding the pilot.
-
Lighting is positioned to avoid direct glare into the cockpit
Check that scene lights, vehicle headlights, flashlights, and portable towers are aimed away from the approach path and aircraft cockpit.
-
Marking lights or cones are visible and properly placed
Verify perimeter markers are visible, stable, and not likely to be displaced by rotor wash.
-
Smoke, dust, or precipitation does not significantly reduce visibility
Assess whether environmental conditions compromise safe landing zone identification or aircraft approach.
Communications and Coordination
This section matters because the landing zone only works when the ground team and aircraft crew share the same call sign, ETA, instructions, and scene control plan.
-
Primary communication link with aircraft or dispatch is established
Verify radio, phone, or other approved communication method is working and monitored by the designated contact.
-
Designated landing zone coordinator identified
Confirm one person is assigned to manage the landing zone, communicate hazards, and coordinate with incident command and flight crew.
-
Aircraft call sign, ETA, and landing instructions confirmed
Document the aircraft identifier, estimated time of arrival, and any pilot instructions or scene-specific requirements.
-
Ground personnel briefed on rotor wash and approach safety
Confirm all personnel in the area have been instructed to remain clear, stay low if directed, and follow the landing zone coordinator's commands.
Final Go/No-Go Readiness
This section matters because it captures the final decision, any unresolved deficiencies, and the sign-off that tells the next person whether the zone is truly ready.
-
Landing zone cleared for aircraft arrival
Final confirmation that hazards are controlled, perimeter is secure, and the zone is ready for landing.
-
Any remaining deficiencies documented
Record unresolved hazards, limitations, or non-conformances that were identified during setup.
-
Inspector signature
Signature of the person completing the landing zone inspection.
How to use this template
- 1. Start by identifying the scene controller and marking the landing zone boundary so everyone knows which area is being evaluated.
- 2. Walk the proposed zone and confirm the surface, diameter, approach paths, and perimeter controls before any aircraft is cleared in.
- 3. Check for overhead utilities, loose debris, fuel, flammables, and other hazards, then remove or isolate anything that could be moved by rotor wash.
- 4. Verify lighting, cones, markers, and visibility conditions, and adjust placement so the cockpit is not exposed to direct glare.
- 5. Establish radio or dispatch contact, confirm the aircraft call sign and ETA, brief ground personnel on rotor wash and approach safety, and record any remaining deficiencies before signing off go/no-go readiness.
Best practices
- Measure the landing area against your local aircraft guidance instead of guessing that the space is large enough.
- Treat overhead wires and poles as a critical hazard and verify the approach path from multiple angles before clearing the zone.
- Secure lightweight items such as tarps, trash, cones, and loose tools because rotor wash can move them into the aircraft path.
- Position lights so they define the zone without shining directly into the cockpit or washing out the pilot’s view.
- Brief every ground person on where to stand, where not to stand, and when to move before the helicopter enters the area.
- Document a no-go condition immediately if visibility, communications, or hazard control cannot be corrected in time.
- Capture the aircraft call sign, ETA, and landing instructions in writing so the handoff is clear if personnel change mid-scene.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
When should I use a helicopter landing zone setup checklist?
Use it any time a helicopter will land at a temporary or improvised scene rather than a permanent helipad. It is especially useful for EMS, disaster response, remote work sites, and incident scenes where the landing area must be selected and cleared on the spot. The checklist helps you document that the zone was evaluated before aircraft arrival.
Who should run this checklist?
A designated landing zone coordinator, scene supervisor, or other trained responder should complete it. The person running it should be able to assess hazards, communicate with the aircraft crew or dispatch, and direct ground personnel. If your organization uses a command structure, this task should sit with the person controlling the scene, not a bystander.
How often should the landing zone be rechecked?
Check it before the first arrival and again whenever conditions change. New hazards can appear from vehicle movement, weather, lighting changes, or scene expansion. If the aircraft is making multiple approaches or the operation continues after dark, re-verify the zone before each landing cycle.
Does this checklist replace aviation or local authority procedures?
No. It supports your local emergency, aviation, or site response procedure and helps standardize the on-scene walk-through. You should still follow the aircraft operator’s landing instructions, local emergency management guidance, and any requirements from the Authority Having Jurisdiction. Use the checklist as documentation, not as a substitute for trained judgment.
What are the most common mistakes this template helps catch?
Common misses include loose debris left in the rotor wash area, overhead wires not fully identified, poor lighting that creates glare, and ground personnel not briefed on approach safety. Another frequent issue is assuming the zone is ready before confirming communications and ETA with the aircraft crew. The checklist forces those items to be verified in order.
Can I customize this for EMS, wildfire, or construction sites?
Yes. You can add site-specific hazards, local radio channels, night operations steps, or agency sign-off fields. For EMS, you may want patient transfer notes and ambulance staging. For wildfire or construction, you may want dust control, equipment shutdown, and exclusion-zone controls.
How does this compare with doing a quick verbal briefing instead?
A verbal briefing is easy to miss under pressure and is harder to audit later. This checklist creates a repeatable record of the landing zone size, hazards, lighting, communications, and final readiness decision. It is better for shift handoffs, multi-agency scenes, and post-incident review.
Can this template be used with digital forms or incident management software?
Yes. The fields map well to mobile inspection forms, incident command systems, and dispatch workflows. You can add photo capture, GPS location, timestamps, and signature fields if your process needs them. Many teams also link it to corrective-action tracking when a no-go condition is found.
Related templates
Ready to use this template?
Get started with MangoApps and use Helicopter Landing Zone Setup Checklist with your team — pricing built for small business.
