How to Identify a Flock Camera Without Guessing

By DeFlock Signs · Last reviewed July 18, 2026

A field guide to Falcon, Sparrow, Condor, Raven, and other Flock hardware

Learn the roadside clues, documented part numbers, common look-alikes, and safe ways to record camera locations with DeFlock and FlockHopper.

You may have passed a Flock camera without noticing it. The most familiar version is not a large red-light camera suspended over an intersection. It is usually a slim black device high on a roadside pole, angled toward traffic, with a solar panel and battery enclosure nearby. It is meant to look unremarkable.

Identifying one is still possible, but the reliable method is to look for a cluster of clues, not one magic feature. Solar panels power traffic counters, weather stations, gate controllers, and other equipment. Black security cameras come in hundreds of shapes. Even within Flock's catalog, different products can share a mounting location while doing very different things.

This guide explains what can be identified confidently from a public vantage point, what deserves a “probable” label, and when only public records can settle the answer. It also explains how to contribute a sighting to DeFlock and how FlockHopper uses that crowdsourced data.

The 60-second Flock camera checklist

A standard fixed Flock license-plate reader is more likely when several of these details appear together:

1. A black, oval or narrow rounded camera enclosure. It often looks more like a flattened black cylinder than a conventional box camera.
2. A dedicated dark pole roughly 12 to 14 feet tall, or a clamp on an existing utility or light pole. A federal court described both installation patterns in United States v. Jackson.
3. A small rectangular solar panel and a separate battery or electronics enclosure. Many installations are designed to operate without a wired power or data connection. Hardwired Flock installations also exist, so a missing solar panel does not rule one out.
4. An angle aimed through traffic rather than across a sidewalk or down at a doorway. Fixed LPRs are commonly positioned to photograph the rear of passing vehicles.
5. A narrow view of a road entrance, exit, or travel lane. The court record says the fixed cameras generally cover two to four lanes, with a deliberately narrow field of view.
6. Placement at an ingress or egress point. Look near subdivision entrances, shopping-center driveways, major through-roads, parking facilities, and the approaches to a jurisdiction.
7. A Flock label or QR sticker visible with optical zoom from public property. The label is stronger evidence than the silhouette, but there is no reason to touch the equipment or climb the pole.
8. A matching point on DeFlock. A mapped location is corroboration, not proof: entries can be missing, stale, duplicated, or misidentified.

The strongest everyday pattern is therefore: black oval camera + rear-plate aiming + roadside pole + solar/battery equipment + a known Flock label or mapped point.

Follow the camera's aim

The direction of the lens is one of the most useful clues because it tells you what the installation is trying to observe.

A fixed Falcon-family LPR is usually aimed at the patch of road where the backs of vehicles pass through its view. It may point diagonally along a lane instead of directly across the road. In a divided road, separate cameras may cover opposite directions. At a subdivision or parking entrance, one may cover arriving vehicles and another departing vehicles.

The camera does not need to be centered over a lane. A roadside view is enough. According to the factual record in United States v. Jackson, Flock's fixed cameras can be triggered by traffic up to about 75 feet away and normally cover two to four lanes. That narrow, deliberate aim helps distinguish an LPR from a broad-view traffic camera intended to show an entire intersection.

At night, an LPR may use infrared illumination, but a visible flash is not a dependable identifier. Do not shine lights or lasers toward the lens to test it. Apart from the danger to drivers and equipment, a field guide should never turn observation into interference.

Flock camera models and identifiers

Flock's names have changed over time, and agencies do not always use them consistently. Newer material may simply say “Flock LPR,” while older contracts and meeting packets say Falcon or Sparrow. The most useful approach is to record both the family name and any part number you can lawfully read.

The product-family distinctions for Falcon, Falcon LR, Falcon SR, Falcon Flex, Sparrow, and Wing appear in a public procurement packet from Prosper, Texas. A State of Michigan contract describes the Falcon Flex quick-deploy package as portable and supplied with a carrying case, charger, mounting clamps, and solar panel.

The numeric part examples come from security engineer Ryan O'Horo's examination of labels and QR data from secondhand devices. His Falcon identification research documents Falcon parts 701-00161 and 701-00203, plus Raven part 703-00005.

Those numbers are useful, but they should not be treated as an exhaustive list. Flock revises hardware, customers keep older units in service, and a single enclosure may contain different lenses, radios, or software configurations.

Fixed Falcon and the familiar Flock LPR

The classic fixed installation is the easiest Flock device to recognize. The Jackson court record calls it a black, oval-shaped camera and says it may sit on a dedicated 12- to 14-foot pole or an existing utility pole. Municipal material from Mukilteo, Washington similarly shows a fixed Falcon installation using mobile data and a solar-charged onboard battery.

In the field, look for a black vertical body with its lens near one end, angled down and along a traffic lane. Nearby equipment may include a rectangular solar panel, wiring running down the pole, and a larger black battery or communications enclosure. Some installations use existing power, so the camera itself and its aim matter more than the panel.

Falcon LR and SR are configurations within this family, not reliable silhouette categories. “Long range” and “short range” describe how the camera is used and configured. Unless a label, deployment plan, or invoice names the variant, the accurate map entry is simply Flock Safety fixed LPR.

Falcon Flex

Falcon Flex is the portable member of the family. The federal court record describes it as a temporary battery-powered camera intended for large events or other temporary settings. The Michigan procurement record adds practical clues: carrying case, charger, clamps, and solar panel.

That means a Flex may be attached to a temporary mast, trailer, sign structure, or other quick-deploy mount rather than a permanent roadside pole. It may move. When mapping a Flex, add the observation date and be prepared for the point to become stale. A one-time sighting should not be presented as a permanent installation.

Sparrow

Sparrow is a legacy or market-specific name associated with neighborhood and private-community LPR deployments. Some public records describe it as smaller or lighter than Falcon, but the families are similar enough that visual certainty is often false confidence.

Location is a clue: a Sparrow name may appear in an HOA invoice or neighborhood entrance plan. Appearance alone is not enough. If you see a Falcon-like unit at a subdivision entrance, map the manufacturer and function you can support, then add “possible Sparrow” only in a note until a label or record confirms it.

Condor PTZ and Condor Bullet

Condor is video hardware, not simply another name for the familiar black LPR. A municipal product page in the Mukilteo meeting packet names two forms:

• Condor PTZ: a white dome-style pan-tilt-zoom camera with a dark moving camera section. It is suited to broad spaces such as parks, intersections, and parking lots.
• Condor Bullet: an elongated white fixed camera on a mounting arm, intended to watch a fixed scene.

The hard part is that Axis, Hanwha, Motorola, Avigilon, and many other manufacturers sell white PTZ and bullet cameras with nearly identical silhouettes. A white dome is evidence of a PTZ camera, not proof of Flock. Look for a readable label, a paired Flock communications enclosure, an agency deployment map, or a contract that names Condor.

A fixed LPR and a video camera can also share a pole. Record each device separately when the mapping system allows it; do not collapse an entire equipment cluster into one guessed model.

Raven acoustic sensor

Raven is not a plate camera. It is an acoustic sensor associated with gunshot and other event detection. A dated CC0 field photograph on Wikimedia Commons shows a compact black rectangular unit mounted vertically on the side of a pole. Its face has a perforated, grille-like surface rather than a visible camera lens. O'Horo's label research documents the observed Raven part number 703-00005.

Because other gunshot detectors, environmental sensors, and wireless equipment can resemble a black perforated box, the grille is not enough by itself. Raven may also be installed in a cluster with cameras, power equipment, or multiple acoustic nodes. Photograph the overall installation from public property so the context is preserved.

Wing and third-party integrations

Wing is the reason a visual guide can never reveal the entire Flock network. Public procurement material describes Wing as an integration for existing third-party LPR or video systems. The physical device may say Axis, Genetec, Motorola, or another manufacturer, or may have no visible Flock branding at all, while its data is available through Flock software.

Do not tag an ordinary third-party camera as Flock merely because it could be integrated. A contract, invoice, data-sharing agreement, or agency system inventory is needed to establish that connection.

Part number, product name, and FCC ID are not the same thing

Camera discussions often turn any number on a label into “the model number.” That creates bad map data.

• Falcon V2 is a named hardware generation.
• 701-00161 and 701-00203 are observed Falcon part numbers encoded in device labels.
• 703-00005 is an observed Raven part number.
• N7NRC76B and WCBN3510A are FCC IDs documented on a Falcon label for internal radio components, cellular and Wi-Fi/Bluetooth, not necessarily the identifier of the complete camera.
• A unique serial, IMEI, SIM number, or MAC address identifies one unit or communications account. It is not the model and should not be republished unnecessarily.

If a photo captures a label, transcribe the family or part number needed for identification and redact unique device identifiers before publishing a close-up. Never climb a pole, open an enclosure, or enter private property to obtain a better label image.

Common look-alikes

Misidentification weakens a crowdsourced map. Before adding a point, consider these alternatives:

Solar traffic counters and transportation sensors

Transportation departments use compact solar systems for traffic volume, travel time, weather, flood, and road-condition monitoring. Some have two or more sensors aimed across lanes. A solar panel proves only that the installation needs off-grid power.

Conventional CCTV

A white bullet or dome camera on a building, parking-lot light, or intersection may be an ordinary video camera. Condor makes those shapes relevant, but the shape is not distinctive. Manufacturer labels and public records matter.

Other ALPR vendors

Motorola/Vigilant, Genetec, Leonardo, Neology, Rekor, and other vendors operate plate readers. DeFlock supports multiple manufacturers. If it is clearly an ALPR but the vendor is uncertain, map it as an unknown ALPR rather than forcing a Flock label.

Gate, utility, and communications equipment

A solar panel beside a driveway may run a gate opener. A black box on a utility pole may be a cellular gateway, power supply, Wi-Fi bridge, or environmental monitor. Find the lens and follow its aim before calling it a camera.

Acoustic sensors from other companies

Raven is not the only pole-mounted sound detector. Look for a label, a consistent Raven housing, multiple sensors in a documented coverage area, or a city contract.

How to document a suspected camera safely

Accurate field notes are more valuable than a dramatic close-up. Observe from a place where you are legally allowed to stand, and never handle a phone while driving. Pull over lawfully, walk from a public area, or let a passenger record the details.

Capture:

• The exact pole location, not the place where you took the photograph.
• Road name and nearest intersection or entrance.
• Which direction the lens faces. Compass direction is useful, but “aimed at eastbound rear plates” is even better.
• The lane or driveway covered. Note whether another unit covers the opposite direction.
• The full equipment cluster. Include the camera, solar panel, enclosures, pole, signs, and nearby devices.
• A medium and wide photograph from public property. The installation context often identifies function better than a tight lens photo.
• Visible words, logos, product family, and part number. Use zoom instead of approaching restricted equipment.
• The date observed. This matters especially for portable Falcon Flex units.
• Your confidence level. “Confirmed by label,” “probable from installation pattern,” and “unknown vendor ALPR” are useful distinctions.

Do not touch, cover, move, open, disable, illuminate, or interfere with the device. Do not trespass. Do not publish a unique IMEI, SIM, MAC address, or serial number when the model and location are all the public needs.

Put the location on DeFlock

DeFlock is the main crowdsourced resource for viewing and reporting ALPR locations. Its open-source project description says the map uses OpenStreetMap data and records camera location, type, and facing direction. It also maintains an identification repository with makes, models, images, and tagging guidance.

The OpenStreetMap Wiki describes the DeFlock mobile app as an OpenStreetMap editor expressly built for adding ALPRs, with current iOS and Android versions. OpenStreetMap's browser-based iD editor is an alternative.

A careful contribution workflow is:

1. Check DeFlock before adding anything. Zoom in and look for an existing point on the same pole. Correcting a record is better than creating a duplicate.
2. Stand safely and place the marker on the actual pole. GPS can drift; use the basemap or aerial imagery to move the point from your observation position to the equipment location.
3. Set the facing direction. The direction should follow the lens, not the direction you happened to be traveling.
4. Identify the device only as specifically as the evidence allows. “Flock Safety” and “fixed LPR” can be correct even when Falcon LR versus SR is unknown.
5. Add the model or part number when confirmed. A visible 701-00161 is useful; a guessed LR/SR designation is not.
6. Include a short evidence note. Examples: “Flock label visible,” “black oval LPR with solar/battery setup; probable Falcon,” or “portable unit observed July 18, 2026.”
7. Review the point and direction before saving. Small placement errors can put a camera on the wrong side of a divided road.

DeFlock is crowdsourced. Treat it as a living research map, not an infallible registry. Accurate uncertainty is better than a confident mistake.

Where FlockHopper fits

FlockHopper is a routing and map companion. According to its OpenStreetMap Wiki entry, it uses camera data from DeFlock and OpenStreetMap to calculate routes that avoid known ALPR positions. Its current iOS listing says users can tap a camera for details and open it in DeFlock.

The practical division is simple:

• Use DeFlock or OpenStreetMap to add and correct camera positions.
• Use FlockHopper to view that data and compare a fastest route with a route around known cameras.

No crowdsourced routing app can promise a camera-free trip. A camera may be new, unreported, portable, privately operated, incorrectly mapped, or connected to Flock through third-party software. FlockHopper can only route around what the underlying map knows.

When visual identification is not enough

For an exact answer, request records from the city, police department, transportation agency, school district, or other public customer. Useful records include:

• The contract, order form, quote, invoice, and renewal.
• The deployment plan or camera-location map.
• A hardware inventory listing product family, model, or part number.
• Installation work orders, permits, and utility-pole agreements.
• The date each unit was installed, moved, replaced, or removed.
• The power and communications configuration.
• A list of enabled services: LPR, fixed video, PTZ video, audio detection, or third-party integration.
• Records identifying privately funded cameras shared with the agency.

Ask for the records in their native electronic format when possible. A spreadsheet can reveal coordinates and model fields that disappear in a flattened PDF. If an agency claims that releasing precise locations would create a security risk, ask for at least the intersection, camera count, product family, and deployment date, and request the legal basis for any withholding.

Public records are especially important for Falcon LR versus SR, Sparrow versus Falcon, Condor Bullet versus an ordinary third-party camera, and Wing integrations. Those distinctions may live in a subscription line item or software configuration rather than a visible enclosure.

Accuracy is the point

Spotting a probable fixed Flock LPR is usually straightforward once you know the pattern: a black oval camera, roadside pole, narrow rear-plate aim, and often a solar panel with battery equipment. Identifying the exact variant is harder. Falcon V2, LR, SR, Sparrow, and Flex are not always written on the outside in a way that can be read from the ground. Condor resembles conventional CCTV. Wing may leave no Flock-branded hardware at all.

That is why a useful public map combines field observation with labels, photographs, public records, and honest confidence levels. Check DeFlock, contribute what you can verify, use FlockHopper with an understanding of its limits, and leave guesses marked as guesses.

Selected sources

• United States v. Jackson, U.S. District Court for the District of Kansas, May 29, 2025.
• DeFlock project repository and DeFlock on the OpenStreetMap Wiki.
• FlockHopper on the OpenStreetMap Wiki and the FlockHopper App Store listing.
• Ryan O'Horo, “Spotting Flock Safety's Falcon Cameras”.
• City of Mukilteo ALPR work-session presentation, July 22, 2024.
• State of Michigan procurement contract, 2026.
• Flock Safety Raven field photograph, Wikimedia Commons, CC0.