Security & Surveillance

Lewisville DFR Log Gap: 486 Flights Not on Public Portal

Lewisville police cite 1,789 DFR flights through Nov 3, 2026; the public dashboard listed 1,303 and stopped at Sept 2. What it means for video teams.

Ceptory Team8 min read
A document concept showing an event log timeline with bracketed entries

TL;DR

DroneXL reported on November 9, 2026 that Lewisville Police counted 1,789 Skydio DFR flights through November 3 while the city's public dashboard showed 1,303 and nothing after September 2. The Oct 20 motel chase cited in press is missing from the public log.

On November 9, 2026, DroneXL reported a gap between what Lewisville Police say their drone as first responder (DFR) program flew and what the city's public flight dashboard shows. The department counted 1,789 flights through November 3; the transparency portal listed 1,303 when Haye Kesteloo checked it on November 9, with no flights after September 2. For teams that manage police drone video, the story is not only accountability. It is operational: when the flight log and the footage archive drift apart, investigators lose the map that tells them which case numbers to open. New Castle County published a six-month summary dashboard in November 2026 without per-flight rows, another transparency format to benchmark.

Related: Knoxville launched its DFR program on November 19 with a public flight log and a 30-day delay option.

What numbers did Lewisville publish in November 2026?

DroneXL summarizes the department's public messaging:

  • 1,789 flights between January 1 and November 3, 2026, described as about six flights per day.
  • 19 drones and 15 trained operators.
  • Official program launch on May 8, 2026, with Skydio aircraft launched from docks under FAA BVLOS authorization.

The city's LPD Transparency page links a DFR flight dashboard that DroneXL says is meant to update automatically. When the editor opened it on November 9, it showed 1,303 flights and stopped at September 2.

That produces a straight arithmetic gap:

SourceFlight countLast flight shownChecked date
Department statement (via DroneXL)1,789Through Nov 3, 2026Nov 9 reporting
Public dashboard1,303Sept 2, 2026Nov 9, 2026

The 486-flight difference is not explained on the transparency page DroneXL read on November 9. If those flights are simply September 3 through November 3, that is about eight flights per day, slightly below the dashboard's August rate of about ten per day.

Public accountability for drone programs ties flight metadata to video exports

What happened on the October 20 call DroneXL highlights?

DroneXL anchors the story with a October 20, 2026 incident behind a motel. The department said DFR 2 launched and reached the scene in under a minute, then followed a man who fled into an apartment complex. Officers arrested him after the drone guided them to a balcony, according to reporting DroneXL cites from the Cross Timbers Gazette.

That narrative is the kind of DFR success story programs use to justify docks and BVLOS approvals. It also exposes why a stale log hurts:

  • Press coverage names the outcome.
  • Residents look at the dashboard for the matching case number and flight entry.
  • If the dashboard ends at September 2, the chase is invisible in the record the chief promised at launch.

DroneXL compares Bellingham, Washington, where it says a Skydio dashboard in October showed flights from five days earlier. Lewisville's gap is measured in months, not days.

Our earlier coverage of Axon's investment in Skydio and exclusive public safety distribution focused on procurement and response-time claims from SEC filings. Lewisville shows the records side: as DFR scales, metadata freshness becomes as visible as arrival time.

How do public DFR dashboards relate to video archives?

DroneXL notes typical dashboard fields: case number when one exists, purpose (emergency call for service, search and rescue, training), flight length, and whether the drone collected video or photos.

Those fields are not the video itself. They are the index card that tells records staff which files to pull. When the index card stops updating, three failure modes appear:

  1. Public trust: Residents cannot reconcile press releases with the portal.
  2. Records response: FOIA teams may know flights happened but lack the matching row to locate exports quickly.
  3. Internal review: Supervisors comparing monthly flight volume to retention storage may double-count or miss folders.

Programs that scale DFR without scaling search hit the same wall described in Evolver DFR and the footage review gap: docks increase clip volume; dashboards alone do not make minutes findable.

The National Institute of Justice publishes Drone as First Responder: Practical Insights into Law Enforcement Implementation. It is policy-oriented, but it reinforces that documentation and community transparency are part of implementation, not an optional appendix.

What does the Lewisville program look like seasonally?

DroneXL breaks down pre- and post-launch volume on the dashboard:

  • 106 flights logged before the May 8 launch.
  • 188 in the remainder of May, 289 in June, 389 in July (peak), 322 in August.

July's peak implies nearly 13 flights per day that month, which is why a six-per-day annual average still masks busy summers. Heat, outdoor events and training blocks can all push DFR sorties without a corresponding rise in trained reviewers if agencies only budget pilots.

For video teams, seasonality matters when you plan indexing. If you only run manual review on incidents, summer peaks sit in cold storage until someone asks. The video review cost calculator helps translate flight counts into hours at risk of never being watched.

What should agencies do when the log and the archive disagree?

DroneXL's editorial asks Lewisville to publish on the schedule its transparency page describes, post September and October flights, and confirm they explain the 486-flight gap before the next statistics release.

For any DFR program, treat that as a checklist:

  1. Define the system of record. Decide whether the dashboard, CAD, or evidence management system owns the canonical flight ID. One ID should appear in all three when video exists.

  2. Automate or admit manual latency. If flights update monthly, say so on the portal header. Automatic claims with monthly reality create the exact gap Lewisville shows.

  3. Tie each published flight to a retention rule. When video or photos were collected, note where files live and for how long. Multimodal video review explains why speech and on-screen text matter when body-worn and aerial feeds are combined.

  4. Separate live viewing from archival search. Live DFR video helps dispatch; post-incident work needs searchable exports. Enterprise video search in natural language describes the capability gap when teams only have timelines.

  5. Write incident reports with the video path in mind. The free incident report template is useful practice for tying narrative, time and camera source before a portal row exists.

Where does Ceptory fit for public safety drone video?

Ceptory does not operate Skydio docks, publish transparency dashboards or replace records management systems. It indexes recorded video you upload or add by URL through the video intelligence API, then lets authorized staff search in natural language across scenes, speech and on-screen text.

Honest fit for a Lewisville-style program:

  • Useful after export: when an agency pulls DFR clips for a case or training review and needs to find a balcony, vehicle or phrase across multiple flights.
  • Not a substitute for the public dashboard, CAD or evidence vault chain of custody.
  • Pricing: $0.042 per minute indexed plus $0.0015 per minute infrastructure, search at $4 per 1,000 queries, first 10 minutes of indexing free (pricing).

Compare with DFR review workflows and FCC drone communications changes if you are also evaluating spectrum and counter-drone sensor feeds alongside DFR video.

How could a records team reconcile 486 missing flights?

Assume the department's 1,789 figure and the dashboard's 1,303 are both sincere counts from different systems. A records unit can still close the gap with a repeatable reconciliation pass instead of ad hoc press fixes.

Start from the dashboard export on November 9, 2026:

  1. Filter by purpose to see whether training sorties, community demos or maintenance hops live only in an internal log. DroneXL says entries include purposes such as emergency call for service, search and rescue and training.
  2. Compare case-number density before and after September 2. If emergency rows disappear but training rows continue elsewhere, you may have an integration break rather than missing flights.
  3. Pull storage totals for the same window. Skydio programs typically retain flight metadata in vendor cloud and video in agency-controlled exports. If terabytes grew in October while the dashboard flatlined, footage may exist without public metadata.
  4. Spot-check three named incidents from local press against both case numbers and file paths. The October 20 motel pursuit is the obvious first test because DroneXL already documented its absence from the portal.
  5. Publish a one-page errata when the gap is explained, including whether automatic updates failed or monthly posting slipped.

That workflow is tedious, but it is cheaper than defending a transparency promise in a public meeting without numbers. It also prepares you for the next consolidation wave: vendor dashboards, Axon-linked Skydio sales channels and municipal open-data portals will not stay aligned unless someone owns reconciliation.

What procurement questions should other cities ask?

Lewisville is a useful template for RFP language even if your department is smaller:

  • Update frequency: Will flight rows hit the public portal within 24 hours, 72 hours, or monthly? Who signs off?
  • Redaction rules: When case numbers are withheld, does the row still appear with a generic purpose code?
  • Video flag accuracy: Dashboard text says whether video or photos were collected. Does that flag match evidence management tags?
  • Export APIs: Can records pull CSV nightly without asking the drone vendor's support desk?
  • Retention parity: If flights age off the dashboard, do retention clocks on video match what the chief described at launch?

DroneXL quotes Chief Brook Rollins telling the Cross Timbers Gazette in May that the department was launching a public-facing transparency portal with policies posted for residents. Procurement should translate that quote into acceptance criteria, not only a marketing slide.

What should Lewisville residents and vendors watch next?

The immediate ask from DroneXL is simple: close the log gap and put the October 20 flight in the portal residents were promised at launch.

For the wider market, the lesson is structural. Skydio DFR adoption is accelerating through channels such as the Axon deal and new mobile viewers such as BRINC LiveOps on iOS, but trust still depends on metadata that keeps pace with flights. When press figures and dashboards disagree by hundreds of sorties, video may exist on a server somewhere, yet the community cannot see how it maps to cases.

Agencies buying DFR this quarter should score vendors on records integration, not only time to scene. If you need to test search on exported clips after you fix the portal, start at Ceptory.

Frequently asked questions

How many DFR flights did Lewisville Police report through November 3, 2026?

DroneXL reports that Lewisville Police said its drones flew 1,789 times between January 1 and November 3, 2026, or about six flights per day on average.

How many flights appeared on Lewisville's public dashboard on November 9, 2026?

DroneXL checked the public dashboard on November 9, 2026 and found 1,303 flights listed, with the last entry on September 2. That is 486 fewer than the department's November 3 figure.

Is the October 20, 2026 motel chase in the public flight log?

No. DroneXL notes the Oct 20 arrest guided by DFR 2 is cited in press coverage but does not appear in the dashboard when the last logged flight is September 2.

What drone platform does Lewisville use for DFR?

DroneXL reports Lewisville flies Skydio drones from docks around the city under FAA BVLOS authorization, with 19 drones and 15 trained operators. The program officially launched May 8, 2026.

Why does a stale flight log matter for video review?

A flight log tells the public and records staff which cases produced video. When the log lags, teams may still retain clips, but auditors cannot match press-reported incidents to case numbers without manual work.

Can Ceptory replace a DFR transparency dashboard?

No. Ceptory indexes recorded video for search and analysis. It is not a public records portal and does not publish flight metadata to residents.

Ceptory

Search your own footage in plain language. The free tier indexes 60 minutes of video.