A Canada goose is a large, heavy bird that moves in flocks, which is why it is disproportionately represented in the strikes that actually damage aircraft. FAA reports that waterfowl account for about 4 percent of civil aircraft strikes involving identified species but 27 percent of the strikes that cause damage. For an airport, an airfield or any property inside the approach, goose management is a safety function governed by its own federal rules rather than a grounds decision. Call Tri-State Geese Patrol on (203) 856-4889.
Waterfowl share of strikes
About 4 percent
Share of damaging strikes
27 percent
Land-use review radius
5 miles, sometimes more
Governing rule
14 CFR 139.337
Because size and flocking behavior are the two things that turn a bird strike into a damaging one, and Canada geese have both.
New York's Atlantic Flyway plan identifies geese near airports as a major safety issue for exactly those reasons. FAA quantifies the imbalance: waterfowl make up about 4 percent of civil aircraft strikes involving identified species, but 27 percent of the strikes that damage aircraft. A bird that is 4 percent of the events and 27 percent of the damage is not an average bird.
The historical record makes the same point from further back. The Atlantic Flyway plan reports waterfowl involvement in 31 percent of bird-aircraft strikes that damaged civil aircraft in the 1991 to 1997 dataset, and 59 percent of the reported monetary losses from wildlife strikes in that period. Those are national historical percentages rather than current local strike rates for any particular field, and they should be read that way, but the shape of the problem has not changed.
FAA is blunt about the stakes overall: wildlife strikes have caused hundreds of deaths worldwide and billions of dollars in aircraft damage. It maintains a national Wildlife Strike Database precisely so that individual airports can investigate their own record rather than reason from national averages.
A flock does the rest. A single bird is one event; a flock lifting into a departure path is many events at once, distributed across a wingspan.
Two operational details follow from the flocking part, and they are the ones that matter to a wildlife coordinator rather than to a statistician. Geese commute, moving between a water refuge and feeding grass on a fairly predictable daily pattern, which means the hazard has a geometry: it runs along a line between two places rather than sitting still on the field. And they lift together when disturbed, so an unplanned disturbance in the wrong place at the wrong moment can create the exact event everyone is trying to avoid. Both are reasons that dispersal on a live airfield is a coordinated activity rather than an errand.
This is the uncomfortable part, and it is worth stating plainly because it explains why the problem keeps returning.
Connecticut DEEP lists airports directly among the habitats that attract Canada geese, alongside lawns, parks, golf courses, athletic fields, ponds, lakes, reservoirs, marshes and rivers. An airfield is a very large expanse of short mown grass with excellent sightlines in every direction and, frequently, drainage or retention water somewhere on or beside it.
That combination is not incidental to how airports are built. The grass is short because it has to be, the sightlines are open because they have to be, and the drainage exists because a large paved area has to put water somewhere. In other words, the site is doing exactly what an airfield is supposed to do and, from a goose's point of view, is close to ideal.
So airside goose management is rarely about removing an attractant, the way it can be on a corporate campus. It is about managing use of ground that cannot stop being what it is.
It also explains why habitat work airside looks different from habitat work anywhere else. On a campus you can let a strip grow at the water's edge and lose nothing. On an airfield, sightlines, drainage and surface requirements are safety constraints in their own right, so the available changes are narrower and have to be agreed with the people who own those constraints rather than proposed around them.
Airport wildlife management is a regulated safety function with its own documents and its own chain of authority. Any provider working here fits into that rather than beside it.
FAA guidance calls for a Wildlife Hazard Assessment following specified triggering events at applicable certificated airports. It is the document that establishes what the hazard actually is at that field, and it is conducted under qualified-biologist guidance where the airport's certification requires it.
Where an assessment leads to one, 14 CFR 139.337 sets out the management-plan requirements for the airports it applies to. This is the governing document for what happens on that airfield, and it is the airport's, not a contractor's.
FAA's national reporting says risk mitigation should consider habitats and land uses within 5 miles of an airport, and sometimes farther. That is why a retention pond on a business park two miles from the fence is an aviation question and not only a facilities one.
New York DEC lists 50 CFR 21.159 as the federal rule covering resident Canada goose control at airports and military airfields, separate from the nest and egg rule at 21.162. Different authority, different conditions, and it belongs to the airport rather than to a vendor.
FAA maintains the Wildlife Strike Database, and an airport's own observation records are what make its assessment and plan current. Work done on a field should feed that record in a format operations can actually use.
Goose presence around a field is not flat across the year, and neither is the risk profile. Knowing which part of the cycle you are in changes what is worth doing that month.
Resident birds are the constant. USDA defines them as geese that nest in the lower 48 states during March through June or reside there April through August, and they are the population an airfield deals with year round rather than seasonally.
The movement risk stacks on top of that. In Connecticut, migrants arrive in early October, movement continues through November, another peak lands in mid-December, and most have gone by mid-January, with a mild winter holding numbers later. New York's Atlantic Flyway plan identifies the Hudson River Valley as an inland winter concentration area and notes that urban areas retain winter birds where there is ice-free water, food and little hunting pressure. Autumn and early winter therefore bring transiting flocks that have no history with your field at all.
Then there is the molt. New York DEC identifies a four to five week flightless period between mid-June and late July, with flight resuming by August. Flightless birds cannot enter the air, which changes the nature of the hazard for those weeks while concentrating birds on the ground, and it is the window in which walking-access controls do the most work.
The practical consequence for an airfield is that a program written for one season is the wrong program for another, and that observation records need to distinguish resident use from transiting flocks if the assessment behind them is going to stay meaningful.
The method is the same as anywhere else. Everything around it is not.
Moving birds without harming them needs no wildlife permit. New York DEC states that no federal or state permit is needed to scare, herd or chase geese, including with dogs or noisemakers, provided no bird is physically harmed. That is the legal basis for Border Collie goose abatement on an airfield as much as on a golf course.
What changes airside is everything around the dog. Access is controlled, movement areas have rules, radio discipline and escort requirements apply, and work has to fit the field's operating tempo rather than a service schedule. None of that is negotiable and none of it is unusual to airport staff, but it does mean a provider who has only worked corporate ponds will need to be brought inside the airport's own procedures.
The other honest limit is the one the research keeps repeating. USDA found that geese hazed at a site returned more quickly than on unhazed days and did not avoid a site for longer than 48 hours after a single event. Connecticut DEEP notes that birds adapt quickly to deterrents with nothing behind them. So hazing reduces use of the ground worked, on a cadence, and it does not create a bird-free airfield. Anyone suggesting otherwise on a safety-critical site is a liability.
USDA's own framing of integrated wildlife damage management puts habitat modification, barriers, repellents and dispersal together, and FAA describes airport programs as habitat work combined with dispersal. One tool, applied hard, is not the model anybody credible recommends.
Most of the properties inside a five-mile radius are not airfields. They are the campuses, courses, parks and ponds that make the surrounding area attractive, and they can be part of the answer. None of this makes a neighboring landowner responsible for aviation safety. It does mean the least expensive place to reduce an attractant is often not the fence line.
A retention pond ringed by mown grass, two miles from a runway, is exactly the kind of off-site attractant FAA's land-use guidance is pointing at. Managing it is good facilities practice and it is also a neighborly aviation contribution.
Water, short grass and open sightlines, which is the same combination, at scale. Courses near a field are frequently among the largest attractants in the area.
Public ground where feeding is common and flock size can build. A no-feeding policy that is actually enforced is a genuine contribution to what happens two miles away.
Standing water and open ground near an airport are worth raising with the airport's own wildlife coordinator rather than managing in isolation.
If an airport has approached you about wildlife attractants on your site, that request comes out of their assessment. Working with it is considerably simpler than being the property named in the next one.
Being specific here matters more than anywhere else on this website.
Non-lethal dispersal using trained Border Collies and handlers, on the areas and the schedule your plan and your operations allow, with observations recorded in a form that feeds your own reporting.
Often the more useful contribution. Reducing what holds flocks on the campuses, courses and ponds inside the surrounding area addresses the attractant rather than the symptom at the fence.
That is conducted under qualified-biologist guidance where your certification requires it. That guidance sits with your biologist, and we work to it rather than around it.
50 CFR 21.159 authority sits with the airport. We hold no such authorization, and any activity under it is yours to conduct or to authorize.
No credible provider does. Hazing reduces use of worked ground on a cadence. The measurable claims are about bird presence and behavior on the areas covered, not about strike outcomes.
On a field with a live assessment behind it, the honest description of our contribution is bounded: reduced goose use of specific ground, recorded consistently, feeding into documents somebody else owns. That is a useful contribution and it is not a safety guarantee, and the distinction matters more here than on any other kind of property we work.
For damage, yes. FAA's figures put waterfowl at about 4 percent of strikes involving identified species and 27 percent of the strikes that damage aircraft. Size and flocking are the reasons, and neither is something a management program can change.
It may well be. FAA's guidance says risk mitigation should consider habitats and land uses within 5 miles of an airport, and sometimes farther, which is why airports raise off-site attractants with neighboring landowners.
Not for hazing that does not physically harm a bird. New York DEC states that plainly. Everything else about airside access, escort, radio and movement-area rules comes from the airport rather than from wildlife law, and it applies in full.
Within the airport's own procedures, which is the only way it should ever be answered. The practical constraints are access, escort and operating tempo, and they are set by operations rather than by us.
No. It fits inside your Wildlife Hazard Management Plan and reports into it. If a provider offers to replace those documents rather than work within them, that is a serious warning sign on a safety-critical site.
Reduced goose use of the ground being worked, recorded and reported so your own assessment stays current, alongside whatever habitat and land-use work the airport and its neighbors can do. A specific reduction figure would be invented, so the reporting deals in what was observed on the ground instead.
In whatever form your operation already uses. The value of observations on a certificated field comes from being consistent and comparable over time, so the format should match your existing wildlife records rather than arrive as a separate document nobody files.
The regulatory obligations may not, but the biology does. The same short grass, sightlines and nearby water attract the same birds, and the size and flocking behavior that make a goose strike damaging do not depend on the size of the airport. What changes is that the documents are yours to design rather than prescribed.
Whether you run the field or the campus two miles from it, the useful first conversation is about where the birds are, what water is nearby and what documents already govern the site. We will tell you what fits inside them.
Call Tri-State Geese Patrol on (203) 856-4889, or send us a message and it goes straight to Bill.
Call Tri-State Geese Patrol on (203) 856-4889 and we will talk through the site, the flock and what a program would look like.
