{"id":197,"date":"2026-07-28T16:18:05","date_gmt":"2026-07-28T20:18:05","guid":{"rendered":"https:\/\/usadg.com\/intelligence-brief\/?p=197"},"modified":"2026-07-28T16:10:00","modified_gmt":"2026-07-28T20:10:00","slug":"hangarkeepers-liability-insurance","status":"publish","type":"post","link":"https:\/\/usadg.com\/intelligence-brief\/hangarkeepers-liability-insurance\/","title":{"rendered":"The Exclusion Sitting on Top of Your Hangar"},"content":{"rendered":"\n
\nIntelligence Brief \u00b7 General Liability<\/strong>
\nYour general liability policy contains an exclusion for property in your care, custody or control. If you operate a hangar, that exclusion sits exactly on top of your largest exposure.\n<\/div>\n\n

A tug operator misjudges a turn. A wingtip meets a hangar door frame. The aircraft belongs to a customer, it is worth eleven million dollars, and it is in your building because you agreed to keep it there.<\/p>\n

Most operators assume the commercial general liability policy handles this. It does not, and the reason is a single clause: hangarkeeper’s liability insurance<\/strong> exists because standard general liability specifically excludes damage to property in your care, custody or control. Everything you are paid to look after is carved out of the policy you assumed was covering it.<\/p>\n\n

What does hangarkeeper’s liability insurance cover?<\/h2>\n

Hangarkeeper’s liability insurance covers damage to aircraft owned by others while in your care, custody or control \u2014 stored in your hangar, parked on your ramp, or undergoing service. It responds to fire, ground-movement collision, hangar rash, falling objects and employee negligence, filling the care, custody and control exclusion in a commercial general liability policy.<\/p>\n\n

<\/div>\n\n

Who needs it<\/h2>\n

The test is not what you call your business. It is whether other people’s aircraft are ever in your possession.<\/p>\n\n

\n
\n
FBOs & ramp operators<\/div>\n

Transient parking, overnight storage, fueling and towing. FBO general liability coverage without a hangarkeeper’s line leaves the core of the operation unprotected \u2014 every aircraft on the ramp is in your control the moment you touch it.<\/p>\n<\/div>\n

\n
Repair stations & MROs<\/div>\n

An aircraft in for a phase inspection may sit in your hangar for weeks, partially disassembled. MRO general liability insurance and hangarkeeper’s do different jobs \u2014 one answers for the work, the other for the airframe while it waits.<\/p>\n<\/div>\n

\n
Defense & government support<\/div>\n

Aviation general liability coverage for defense contractors takes on a different character when the airframe belongs to a program. Damage to a government aircraft is not merely a repair invoice \u2014 it is a schedule slip on a contract with a delivery date.<\/p>\n<\/div>\n

\n
Avionics, paint & interior shops<\/div>\n

A specialty shop can hold a customer’s airframe for weeks \u2014 panels open, high-value avionics exposed, the aircraft worth far more than the invoice for the work. Operators who do not think of themselves as full repair stations often carry limits sized to the job, not to the hull sitting in the bay.<\/p>\n<\/div>\n<\/div>\n\n

<\/div>\n\n

The two structures, and why the difference matters<\/h2>\n

This is the part that gets glossed over in a quote comparison, and it is where two policies that look alike behave completely differently after a loss.<\/p>\n

Legal liability form.<\/strong> The policy responds only if you are legally liable for the damage \u2014 that is, if negligence can be established. If a hailstorm collapses the hangar roof onto three customer aircraft and nobody was negligent, a legal liability form may not respond at all. The customer’s own hull insurer pays, and then, quite possibly, comes looking for you anyway.<\/p>\n

Direct primary form.<\/strong> The policy responds to covered damage regardless of fault. It costs more. It also removes the argument, which is precisely what you are buying \u2014 because the argument happens at the worst possible moment, with a customer standing in your hangar looking at their damaged airplane.<\/p>\n\n

\n

Two hangarkeeper’s policies at the same limit can be a factor of ten apart in what they actually pay. The limit is the number people compare. The form is the number that matters.<\/p>\n<\/blockquote>\n\n

How the limits are structured<\/h2>\n

Hangarkeeper’s limits are written two ways at once, and both have to be right.<\/p>\n

There is a per aircraft<\/em> limit and a per occurrence<\/em> limit. The first caps what the policy pays for any single airframe. The second caps what it pays for one event, no matter how many aircraft that event touches.<\/p>\n

The failure mode is easy to describe and expensive to discover. An operator carries a limit sized to the most valuable aircraft it ever handles, which feels prudent. Then a hangar fire involves six aircraft simultaneously, the per-occurrence limit is exhausted well before the individual claims are, and the shortfall lands on the operator. Set the per-aircraft limit against the most expensive airframe you will ever accept. Set the per-occurrence limit against the worst night your hangar could have with everything in it.<\/p>\n

One more structural point, because it decides who actually pays. Hangarkeeper’s is excess<\/em> over the aircraft owner’s own hull policy in most placements \u2014 the owner’s insurer pays first, then looks to you for what it paid. That subrogation claim is the real-world shape of most hangarkeeper’s losses, and it is why the limit needs to contemplate not just the damage but the recovery action that follows it. A hangar lease or service agreement will often try to shift that burden by contract; whether your policy actually responds to a liability you assumed in writing depends on how the contractual liability language is drafted, and it is worth reading before signing rather than after.<\/p>\n

The coverage also has edges worth knowing before a claim finds them: aircraft in flight generally fall outside it, subcontracted work may not be picked up, and aircraft left on the field after hours can raise questions about whether they were in your custody at all. None of these are unusual. All of them are worth resolving at placement rather than at loss.<\/p>\n\n

\n
ReflexOS\u2122 \u00b7 Identify \u2192 Flag \u2192 Discuss \u2192 Adjust<\/div>\n

A hangarkeeper’s limit is usually set once and revisited at renewal, while the exposure underneath it changes constantly \u2014 a new customer with a larger aircraft, a busier season, a hangar packed tighter than it was in March. ReflexOS\u2122<\/strong> supports proactive liability exposure monitoring for contractors<\/strong> by reading what the operation already records \u2014 movements, storage, work in progress \u2014 and surfacing the point at which the values on the field have outgrown the limit on the policy. Identify<\/strong> the drift. Flag<\/strong> it. Discuss<\/strong> it with your broker. Adjust<\/strong> deliberately, before the busiest night of the year is also the night you find out.<\/p>\n<\/div>\n\n

<\/div>\n\n

Placing it properly<\/h2>\n

Hangarkeeper’s is rarely bought alone. It sits alongside premises liability for the facility itself, products and completed operations if you perform work, and the broader aviation general liability<\/a> program that responds when the injury is to a person rather than an airframe. Written separately by separate parties, those policies develop gaps between them \u2014 and the gap is always discovered by a claim.<\/p>\n

USADG is a specialized independent insurance broker to the aviation, aerospace and defense community. It places<\/strong> and structures<\/strong> hangarkeeper’s and aviation liability programs with A-rated underwriting partners, and it advocates<\/strong> for clients on claims. The value in a specialist is knowing which form to write, where the per-occurrence limit should sit for your actual operation, and which endorsements close the seams between policies before anyone needs them to. The lines are set out on the USADG coverage page<\/a>.<\/p>\n\n

\n

Nobody reads the care, custody and control exclusion until the wingtip is already bent. It has been in the policy the whole time, doing exactly what it says.<\/p>\n<\/blockquote>\n\n

\n
<\/div>\n
Available Exclusively to USADG Clients<\/div>\n

U.S. Aerospace Defense Group places and structures hangarkeeper’s, aviation general liability and products programs for FBOs, repair stations and defense support operations, working with A-rated underwriting partners \u2014 with the form, the limits and the endorsements set against the operation you actually run. The ReflexOS\u2122 overlay keeps the exposure picture current between renewals.<\/p>\n


\nRequest a Briefing<\/span><\/a>Quantum Call \u2192<\/a>
\n<\/span>\n<\/div>\n\n

\n
Tags & Distribution<\/div>\n

\n#HangarkeepersLiability #AviationInsurance #AviationGeneralLiability #FBO #MRO #RepairStation #CareCustodyControl #AircraftInsurance #HangarRash #AviationRisk #DefenseContractor #GovCon #InsuranceBroker #AviationSafety #ReflexOS #SDVOSB #USADG #IntelligenceBrief\n<\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

Standard general liability excludes property in your care, custody or control. If you run a hangar, that exclusion sits on top of your largest exposure.<\/p>\n","protected":false},"author":1,"featured_media":198,"comment_status":"closed","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[10],"tags":[],"class_list":["post-197","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-general-liability"],"_links":{"self":[{"href":"https:\/\/usadg.com\/intelligence-brief\/wp-json\/wp\/v2\/posts\/197","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/usadg.com\/intelligence-brief\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/usadg.com\/intelligence-brief\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/usadg.com\/intelligence-brief\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/usadg.com\/intelligence-brief\/wp-json\/wp\/v2\/comments?post=197"}],"version-history":[{"count":1,"href":"https:\/\/usadg.com\/intelligence-brief\/wp-json\/wp\/v2\/posts\/197\/revisions"}],"predecessor-version":[{"id":199,"href":"https:\/\/usadg.com\/intelligence-brief\/wp-json\/wp\/v2\/posts\/197\/revisions\/199"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/usadg.com\/intelligence-brief\/wp-json\/wp\/v2\/media\/198"}],"wp:attachment":[{"href":"https:\/\/usadg.com\/intelligence-brief\/wp-json\/wp\/v2\/media?parent=197"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/usadg.com\/intelligence-brief\/wp-json\/wp\/v2\/categories?post=197"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/usadg.com\/intelligence-brief\/wp-json\/wp\/v2\/tags?post=197"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}