OBSERVE / PREDICT / EVALUATE / DECIDE
Understand the next constraint.
Explainable forecasts and operator-led decisions across the airport.
Archived snapshot · schematic facilities · no live feed
Evidence & connection status
Replay uses the selected departure subset; the complete collected daily schedule is available below. Arrival rotations and exact stand assignments are simulated; historical stand observations are unavailable.
Full-day DDFS · 366 arrivals + 358 departures · Download DDFS CSV · Capture dates, counts and sources
Building connected runway routes…
Drag to orbit · right drag to pan · wheel to zoom. Navigation automatically stops aircraft follow. Full-screen controls remain inside the viewer. Vehicle routes respect mapped one-way links. Road interactions are visual, not a congestion model.
RET, navigation aids & obstacle surfaces
LOC, GP, ILS DME and BIA DVOR/DME coordinates come from AAI AD 2.19. Fixture shapes and heights are schematic. RETs A5-A8 and H4-H7 follow mapped paths; the eastbound simulation selects A6/H5 for B/C and A5/H4 for E. AAI published procedures and aid coordinates.
OLS colours: blue approach, amber take-off climb, violet transitional, green combined inner horizontal, coral extended conical. Preset: Indian Schedule II (2015), Code 4 instrument runway: 300 m approach inner edge; 60 m offset; 15% divergence; 3,000 m at 2%, 3,600 m at 2.5%, 8,400 m horizontal. Take-off: 180 m inner edge, 12.5% divergence to 1,200 m; 15 km at 2%. Inner horizontal: 4 km around combined runway ends at 45 m; transitional 1:7; extended conical 5% to 300 m.
Flat common datum study, not surveyed AMSL. This historical preset is not a validated current BLR safeguarding model. Terrain, threshold elevation differences, OFZ, outer horizontal, adjoining airports, PANS-OPS and CNS protection are not included. Government reference, Schedule II pages 71-74.
Enter a test object to compare against the lowest modelled surface. This does not assess real-world obstacle clearance.
T2 expansion & landside study
Teal: south processor extension, two links and southern concourse; 10 illustrative future gates F01–F10, an expanded 1,100 × 320 m apron and dual 23 m-wide proposed taxi lanes P2-A/P2-B at 80 m centre spacing. All dimensions and end connections are study assumptions, not approved clearances. These are study dimensions estimated against existing T2. Future gates are excluded from DDFS allocations. The fourth image supplies road topology only; its terminal and cargo proposals are not adopted. Road levels +6 m / −5 m are assumptions, and the road study overlays the mapped existing network.
Eastern cross-field taxiways P / Q
The two mapped eastern connectors join the north and south taxiway systems. Pavement width is 23 m from the AAI aerodrome chart; outer strip extent follows an approximate map tag. Use the Cross-field viewpoint to inspect both links and their network connections. Coloured inspection traces are not pavement markings. The western elevated pair (WCT) is modelled separately below.
Dual parallel taxiway ring · WCT
Loading the ring and elevated cross-field model…
Human-centred connection intelligence · v0.14
Plan connection allowances for walking pace, assistance handovers, baggage deadlines, terminal changes and disruption. Compare arrival and departure banks and directional shuttle capacity. SQ flights are allocated to T2 by user instruction.
Open connection and wave-bank planner ↗ · Passenger demand heat map ↗
Source library & imported modules
Additional references: Esri Wayback imagery · NASA Worldview · SOM T2 design reference · Reviewed map / plan / imagery register. Viewer access does not imply permission to redistribute imagery; no new satellite texture has been imported. Current approved Phase 2 drawings remain unavailable.
Original AeroNOVA TIA console · demo reference ↗ · Original BARDI July 2026 ↗ · BIARDI / DDFS planning engine ↗
TIA Observe → Detect → Predict → Compare → Operator decision is connected to this replay. Original console sample flights, risk scores and named owners are not observations. BIARDI supplies route geography; its demand forecasts remain planning assumptions.
Predictive watchlist
Rule-based model forecasts; not detected live airport incidents. Select an alert to inspect its flight.
Intervention comparison
Operator decision log
TERMINAL DESIGN STUDY
Passenger journeys, floor by floor.
Operational flight board
| Flight | Aircraft | Runway | Stand | State | STD | Delay |
|---|
Airside markings & reference drawings
North: 09L / 27R · South: 09R / 27L. Both runway surfaces: 4,000 × 45 m in the AAI aerodrome chart, dated 27 November 2025. Mapped endpoints remain approximate. The former 60 m south-runway map tag is superseded in this rendering.
White: runway guidance. Yellow: taxi / stand guidance. Red equipment boundaries and hatched stand areas: conceptual layout. HOS / TOS remain inferred service roads. Seven RET holding references use published AAI positions snapped to mapped taxiway geometry within 30 m. A6 differs by about 33 m and retains an inferred marker pending review; other holding markings remain illustrative A2 patterns. Aircraft-specific stop positions, ILS sensitive areas and masterplan geometry are not verified.
AAI aerodrome chart ↗ · ICAO Annex 14 Volume I, Chapter 5 ↗
Stand markings use the same nose-wheel stop and lead-in geometry as the simulation. This is an Annex 14 convention study; full compliance and masterplan conformity have not been established.
Model provenance and operating limits
Code B, C and E models use illustrative 20 m, 34 m and 60 m wingspans. Parked envelopes are sampled against the mapped apron. Runway reservations include modelled crossings. Wind, real ATC procedures, aircraft-specific turning envelopes, pavement strength and wake categories are not validated. Terminal floor plans and future expansion limits are not approved drawings. The WCT is an indicative Code F planning model built from public reporting; it is not the BIAL design. © OpenStreetMap contributors · ODbL.