Dunvale
Reports/Aviation Pulse/2026-04-20
Published

Aviation Pulse - April 20, 2026

Generated Apr 20, 7:58 AM PDT

Dunvale Intelligence
Aviation Pulse Monday, April 20, 2026

Aviation Pulse - April 20, 2026

Generated 7:56 AM PDT

Aviation Pulse · Daily

Airports monitored 15 14 clear
With active delays 0
Avg delay

Analyst Notes

Current FAA status indicates no mandated operational slowdowns at monitored border airports, suggesting standard throughput efficiency for airfreight movements. Operators should anticipate routine flow, though ground handling capacity and customs inspection backlogs remain primary variables. Closely monitor the US-Mexico corridor, as staffing constraints at customs facilities are the most likely source of non-FAA delays.

Data sources: CBP BWT, CBSA, NWS, FAA ASWS, FRED, Banxico, INEGI IMMEX, STB Rail, Census Bureau, Statistics Canada, Federal Register

dunvale.com | RSS Feed

This report is generated from public government data. It is not investment advice. Dunvale Intelligence makes no warranties regarding accuracy or completeness.

Commercial coverage

Cited border evidence with source policy for sales, operations, and agent workflows

Border Pulse

Coverage options

4

Listed service

1

Custom quote

2

Planned

1

Recommended next step

Choose the listed Laredo service where it fits, or request custom review for San Ysidro, Otay Mesa, Texas lanes, Detroit/Windsor, or another priority crossing.

Pricing

Laredo has a listed monthly service. Otay Mesa and Detroit/Windsor are available for custom quotes. Additional crossings remain in coverage planning.

Account setup

Account teams can activate delivery after scope, access, and billing are approved.

Delivery controls

Commercial delivery, account access, billing, alerts, and automated workflows require an approved account setup.

No delivery, alerts, or account keys are activated from public pages.

Laredo policy watch

2 MVE/USMCA dates tracked for Laredo operating context.

Laredo

Market context

4 operating context families drawn from 268 reports.

Coverage detail

Laredo Border Pulse

commercial ready; listed price; $199/month; 14 facts.

Choose the listed Laredo service where it fits, or request custom review for San Ysidro, Otay Mesa, Texas lanes, Detroit/Windsor, or another priority crossing.

Otay Mesa / San Diego planned coverage

custom review ready; not yet priced; 16 facts.

Choose the listed Laredo service where it fits, or request custom review for San Ysidro, Otay Mesa, Texas lanes, Detroit/Windsor, or another priority crossing.

Otay Mesa custom coverage review

custom review available; custom quote; 16 facts.

Choose the listed Laredo service where it fits, or request custom review for San Ysidro, Otay Mesa, Texas lanes, Detroit/Windsor, or another priority crossing.

Detroit / Windsor custom coverage review

custom review available; custom quote; 21 facts.

Choose the listed Laredo service where it fits, or request custom review for San Ysidro, Otay Mesa, Texas lanes, Detroit/Windsor, or another priority crossing.

Why It Matters

Analyst summary available

Claim Policy

Cited report/packet claims only

Use cited packet/report evidence for claims; weather, road, policy, and map overlap stays contextual unless evidence proves causality.

Packet or replay citations must expose evidenceId, claimBearing, claimGuidance, evidenceMode, and source_ref claim policy.

Broad source-level claims also require sourceClaimAudit review, /v1/sources claimBearing=true, sourceFactHealth.total > 0, sourceFactHealth.claimBearingPolicyRows > 0, sourceFactHealth.parserLagHours within maxParserLagHours, sourceFactHealth.futureEventsBeyond7d=0 for current road claims, no pending/failed embedding backlog for semantic-only claims, no degraded-run caveats, and no blocking claimWarnings for the source family.

Raw-current, raw-only, stale, no-row, scheduled, planned, future, retired, unknown, parser-lagged, degraded-run, embedding-backlog, feed, search, and briefing source rows remain caveated context unless report citations explicitly review them.

Planned/future traffic rows must be labeled non-current planning context and not cited as current evidence.

Model Generation Policy

modelProvider/modelVersion: local / gemma4:e4b

Lane: local_report_generation

OpenAI content/report lanes require explicit gates and use store:false; no-call previews write local artifacts only.

Generated reports inherit cited report text, source facts, packet evidence, saved source_ref claim policy, and /v1/sources source-fact health: sourceFactHealth.total > 0, sourceFactHealth.claimBearingPolicyRows > 0, parser-lag/future-row/embedding-backlog/degraded-run checks, and no blocking claimWarnings.

Generated report wording is reusable only inside cited report text, cited packet evidence, or saved source_ref claim policy.

Broad source-level claims require sourceClaimAudit review, /v1/sources claimBearing=true, sourceFactHealth.total > 0, sourceFactHealth.claimBearingPolicyRows > 0, sourceFactHealth.parserLagHours within maxParserLagHours, sourceFactHealth.futureEventsBeyond7d=0 for current road claims, no pending/failed embedding backlog for semantic-only claims, no degraded-run caveats, and no blocking claimWarnings.

Raw-current, stale, no-row, scheduled, planned, retired, unknown, planned/future, parser-lagged, parser-incomplete, degraded-run, and embedding-backlog rows remain context only unless cited evidence says otherwise.

Do not infer causality from co-occurrence; weather, road, policy, and wait overlap stay contextual unless evidence proves cause.

Persisted with report: no

Key Metrics

airports clear14
airports monitored15
airports with delays0
average delay minutes0

Report Info

TypeAviation Pulse
Cadencedaily
ScopeNational

Subscribe

RSS Feed

JSON API: GET /public/reports/aviation_pulse/2026-04-20