Columbus forward signals
Predictive surface — what the platform projects, when each call is expected to resolve, and the score impact if realized. Resolutions feed the public Predictions Ledger.
86 OE/AAA determinations in the development footprint — 18 structures studied near airspace, tallest 40 ft AGL; 19 crane/construction filings; 18 facility airspace studies.
Cumulative airspace-study footprint from FAA OE/AAA determinations geo-matched to this market — a development-intent indicator (towers, helipads, cranes studied for airspace effect). Density & composition, not a velocity claim.
Near-term (≤ 60 days)3
- Operatormedium30-180 days for operational follow-up+5 pts3 operator market expansion events tracked (0 high confidence). Operator announcement — follow-on operational events typically follow.3 events classified in last 90d, most recent 2026-06-20
- Infrastructuremedium60-90 days from filing3 faa corridor filing events tracked (0 high confidence). FAA aeronautical study cycle for corridor or facility determination.3 events classified in last 90d, most recent 2026-04-27
- Infrastructuremediumnext 90 daysMarket shows positive momentum across recent signals; watch flagged improvingMarketWatch outlook based on 30-day signal aggregation; track record limited (system deployed Apr 2026)
Medium-term (60–180 days)1
- Infrastructurehigh3-12 months for build/permit cycle+15 pts48 infrastructure development events tracked (1 high confidence). Infrastructure development announcement — typical permit-to-operational cycle 3-12 months.48 events classified in last 90d, most recent 2026-06-29
Long-term (180+ days or unscheduled)0
Each forward signal here resolves against the public Predictions Ledger. First verifications start June 16, 2026; the public scoreboard ships with Pulse Issue 6 in July, after which every Pulse carries a running “Last Month's Calls” track record.
Need more depth on Columbus?
The above is the light analytical layer. Institutional engagements unlock primary-source citations per factor, historical factor-level snapshots, methodology overrides with rationale, and analyst notes — at the depth a deployment decision actually requires.
Talk to us about depth access