What Are “Flyovers” in Bird Monitoring?

If you’re new to bird surveying, you’ve probably heard someone mention “flyovers” and wondered what that means. Are they talking about birds that are flying? Migrating birds? Soaring? The answer is – kind of all of the above, but with a specific meaning in the context of bird monitoring.

Let’s break it down.

What Is a Flyover?

In bird monitoring, a flyover refers to a bird that is observed flying over a point or area without showing any signs of using the surrounding habitat at your survey site. These birds are just passing through the airspace above you – they’re not perching, nesting, feeding, or interacting with the environment where your survey is taking place.

You can think of them as birds “in transit.”

Why Does It Matter?

The main goal of most bird surveys is to assess which birds are using a particular area (e.g., a particular habitat, an impact area, a wetland, etc.). If a bird is just flying over your point count or transect area but not engaging with the habitat, it’s not technically using that habitat. Including flyovers alongside your other observations could lead to inaccurate conclusions about the activity of species within the area you are surveying.

So, understanding and correctly recording flyovers helps ensure your data reflect the birds associated with your site, not just birds passing through.

How to Record a Flyover

Most standardized bird monitoring protocols (like point counts, transects, or area searches) have a way to separately document flyovers. Here’s a typical approach:

  • If you see or hear a bird flying over and you’re confident it never landed or used the habitat, mark it as a flyover.
  • Ensure your datasheets have a place to denote the flyover status of an observation, such as a distance bin (in point counts) or a detection cue.  Avoid recording this information just in the comments of your data. Several AKN tools have functionality related to flyovers, but this information is not accessible when stored in a notes field. See more about this below.”

Examples of Flyovers

Here are some common examples:

  • A flock of geese honking overhead while you’re surveying a forest plot.
  • A raptor soaring high above your grassland point count that never drops to hunt.
  • A lone gull cruising inland over a desert survey site.

In each case, the key detail is: the bird is not using the habitat you’re studying – just the airspace above it.

When It’s Not a Flyover

Not every bird in the air is a flyover. If a bird:

  • Circles above your site hunting (e.g., a hawk scanning a field),
  • Lands briefly in a tree or on the ground,
  • Vocalizes repeatedly from overhead and seems to be interacting with the area (e.g., a territorial male singing in flight),
  • Swifts and swallows foraging over an area (since they are eating bugs from the habitat below)

…it might count as being associated with the habitat, not just passing through.

How the AKN Supports Flyover Data

The AKN supports flyover data collection and helps users manage it meaningfully across tools and datasets. For many AKN Protocols, observers can often indicate whether an observation was a flyover in existing fields, such as distance bin (point counts) or detection cue.

More importantly, once data are in the AKN, you retain the power to filter and analyze based on those designations. For example:

  • In tools like Analyst, users can choose to include or exclude flyovers when generating summaries or running queries.
  • If your objective is to assess habitat use, you can filter out flyovers to avoid misrepresenting site-level usage.
  • If you’re studying migration timing or flight corridors, you might want to focus on flyovers specifically.

The AKN system treats flyovers as a distinct attribute in your data, which means your analysis stays flexible and your data stay useful – no matter your research or reporting question.

Here are two examples of AKN Protocols that record Flyovers differently:

Final Thoughts

Flyovers are easy to overlook – or accidentally include – especially when you’re just starting out. But getting into the habit of noting whether a bird is truly using your survey site or just flying by is a great skill that will improve the quality and reliability of your data.

And with tools like those in the AKN, you don’t have to worry about losing those observations or being stuck with a one-size-fits-all dataset. The system is built to help you record, filter, and analyze flyover data in ways that support your unique monitoring goals.

So next time you’re in the field, keep an ear and eye to the sky – but remember to ask yourself: “Is a bird flying or is it a flyover?”.

DoD AKN Standard Sampling Methods – Species Checklist

Biologists across DoD are employing a diversity of bird monitoring protocols in support of their natural resource management activities. This diversity of protocols makes combining data and analyses among installations and service branches unnecessarily challenging and can lead to inaccurate analyses that do not fully support an understanding of how activities on installations are affecting bird populations from local to regional scales.

One of the key motivations behind the DoD AKN Program is to promote consistent avian data standards across the DoD. To meet this objective, the Team has begun to develop and recommend standardized field sampling methods and AKN Protocols based on DoD’s most common management and research needs.

The first of these standardized sampling methods is a Species Checklist Area Search! Check it out here:

DoD AKN Standard Sampling Methods – Species Checklist

What is a Species Checklist?

Species checklists are a simple way to record both incidental and comprehensive observations of bird species observed on your installation that don’t fit a traditionally structured survey (e.g., point counts, line transects, etc.).

Like all protocols in the AKN, there is some minimum information required per event (i.e., per observation):

  1. The observation must be of a living bird
  2. The observation should include the date (Month/Day/Year)
  3. The observation needs to be associated with a sampling unit (see below)
  4. The observation includes the name of the observer
  5. The observation has a specified start and end time on the date the data were collected

Visit the Portal page for more information on this checklist protocol and check back often as the Team is constantly developing methods and protocols your common (and uncommon!) avian data collection needs.

Have a suggestion for our next protocol to develop? Contact the Team at DoDAKN@erdc.dren.mil

Mission-Sensitive Species Profile and Recommended AKN Sampling Protocols – Pinyon Jay

DoD Partners in Flight has developed a list of the bird species occurring on DoD installations that have the highest potential to impact the military mission should they become Federally listed under the Endangered Species Act, termed Mission-Sensitive Species (MSS). 

The DoD AKN Team is continually working with DoD and non-DoD subject-matter-experts to review the best-available guidance for standardized field sampling methodologies for each Mission-Sensitive Species and ensuring those methods are translated to AKN Sampling Protocols to be used in your Project.

The first MSS sampling guidance is now available on the MSS page for Pinyon Jays which describes and compares two recommended standardized field sampling methods and their associated AKN Sampling and Site Condition Protocols.

Pinyon Jay Standardized Sampling Methods

Keep an eye on the MSS page for the next species profile and standardized sampling methods.