Landing zone billing that keeps coordination visible

Document scene safety, aircraft timing, apparatus standby, and related incident context for review before carrier follow-up.

View FAQ
New Landing Zone Claim
Auto-save every 30s
Landing Zone Claim
Form Type: LZ - Landing Zone

Fire Department Information

Fire Department Name *
Sunnydale Fire Department
Fire Chief First Name
Allan
Fire Chief Last Name
Finch
Representative First Name *
Brian
Representative Last Name *
Shaw
Title/Rank
Fire Captain

Incident Information

Landing zone location and patient context
Landing Zone Location *
Patient transport context

The LZ may be temporary. The coordination still matters.

Without Onsite
LZ treated like a footnote
Landing zone work becomes a side note.
Traffic control, perimeter, and hazard details are thin.
Air medical timing disconnects from the incident.
Add-on LZ review gets lost after the transport.
With Onsite
Coordinated LZ support
Safety, command, and aircraft coordination stay linked.
Perimeter, standby, and hazard work are documented.
LZ support is reviewed with the related incident and available insurance path.
Status appears in the same recovery reporting.

Treat the landing zone like a coordinated service, not a footnote

Landing zone support can look brief on paper. The real work is setup, perimeter, hazards, EMS coordination, standby, and tying the LZ back to the incident that created it.

01
What happened
Keep LZ setup, location, air medical timing, EMS coordination, command notes, and patient transport context together for review.
02
Who responded
Show responding units, apparatus staging, standby support, mutual aid, command, and scene-control resources tied to the LZ.
03
What was used
Document perimeter control, traffic control, hazard checks, power-line review, debris removal, apparatus standby, and fire suppression standby when part of the response.
04
Related incident
Keep the LZ connected to the auto, rescue, fire, medical, or mutual aid incident that created the air medical response.
05
Carrier follow-up
Track insurer responses, pending claims, denial reasons, recovered activity, and open follow-up with the related incident context.

What a landing zone review actually needs

Landing zone support may look brief on the report, but the review needs the setup, safety, standby, aircraft coordination, and related incident context attached.

01

What the department submits

Submit the LZ details and the incident context that created the air medical response.

  • LZ location and setup
  • Related incident details
  • Command and EMS notes
  • Hazard assessment
  • Apparatus standby time
  • Air medical coordination
02

What Onsite does with it

Onsite keeps the LZ work tied to the incident and prepares the packet around the documented support provided.

  • Organizes LZ setup details
  • Connects related incident context
  • Documents scene safety work
  • Prepares recovery packet
  • Tracks carrier follow-up
  • Reports LZ activity by status
03

Billing versus payment

Landing zone support can be billed when documentation and the related incident context support insurance-company review.

  • Billing may be tied to another incident
  • Payment depends on available coverage
  • Claim activity matters
  • Policy limits may apply
  • Carrier response controls outcome
  • Onsite bills insurance companies only

Track landing zone activity without separating it from the rest of the call

Landing zone support can be hard to explain after a scene clears. The Recovery Hub keeps LZ activity, related incident context, follow-up, denial notes, and monthly reporting in the same leadership view.

Submitted
Recovered
Pending
Denied
Open
Submitted LZ activity
Related incident references
Add-on service status
Monthly reporting by service line

Eligibility for recovery depends on local ordinance or policy, applicable state law, documentation, responsible-party information, available insurance coverage, whether an insurance claim exists, policy limits, and carrier response. Onsite Fire Billing supports administrative recovery workflows and does not provide legal advice.

Common questions before a recovery review

Read the full FAQ
Can landing zone support be billed?

Yes. Landing zone support can be billed to insurance companies when documentation and the related incident context support review. It is often tied to another incident, and payment depends on available coverage, claim activity, policy limits, and carrier response.

Is landing zone billing always standalone?

Not always. Landing zone support is often connected to the incident that created the need for air medical transport. Onsite keeps the LZ response tied to that incident context when preparing the packet and tracking carrier follow-up.

What landing zone documentation matters most?

Helpful documentation includes LZ setup, perimeter control, hazard assessment, scene safety, apparatus standby, EMS coordination, air medical coordination, traffic control, mutual aid, timing, and the incident that created the landing zone response.

Review LZ activity before it becomes an afterthought

Identify whether recent landing zone activity has the related incident context, scene-safety documentation, available insurance information, and reporting detail needed for review.

Landing Zone Billing for Fire Departments | Onsite Fire Billing