Airport incursions are reports of unidentified or unauthorized objects operating near airports, approach paths, runways, or controlled airspace. The object may ultimately be a drone, balloon, aircraft, bird, laser source, astronomical light, or something unresolved. “Incursion” describes the operational problem—an unexpected presence in a protected environment—not a conclusion about exotic origin. Airports demand rapid decisions because even a small object can disrupt traffic or endanger an aircraft during takeoff and landing.

The Federal Aviation Administration separates several overlapping hazards. Runway incursions involve incorrect presence on a protected runway; unauthorized drones create a low-altitude collision and security risk; laser illumination can impair crews; and UAP reports cover observations not immediately identifiable. Current FAA procedures require air-traffic personnel to elevate pilot or controller UAP observations through the Domestic Events Network, recording position, altitude, direction, description, and radar depiction when available.

A cluster of airport reports can cause diversions, closures, or law-enforcement response before identification is complete. That caution is appropriate, but operational disruption does not authenticate every sighting. Multiple witnesses may be observing the same aircraft or celestial source, and social attention can increase reporting of unrelated lights. Radar, radio logs, airport surveillance, Remote ID data, weather, and synchronized video are more useful than a count of impressions alone.

Airport cases sit at the intersection of Commercial Pilot Sightings and UAP & National Security. Their priority comes from collision risk, airspace control, and the possibility of surveillance or interference. A responsible case record preserves the immediate safety response while allowing later identification; it does not force controllers to decide an object's ultimate nature during a time-critical event.