Crashfree India School Safety Index DELHI · JAIPUR · PUNE

Schools / Pune

Road-environment audit · SSI v0.3

The road outsideKendriya Vidyalaya No.1 AFS Pune

Air Force Station, Near Canara Bank, New Project Area, HWR9+RQ7, Lohegaon Road, Lohegaon, Pune International Airport Area, Lohegaon, Pune, Maharashtra 411032, India18.59203, 73.91942audited 2026-09-04
22/100
Unsafeprovisional band
Unsafe. Very little on this road protects a child crossing to the gate.
Of the five things we check, 3 are missing entirely.
This road · 22
0 · no protectioncomplete protection · 100
Checked twice, independently
Two AI readers on separate accounts · corrections logged in public
4
Confirmed
1
Corrected
0
Unresolved
See how each was judged
Of 153 roads scored so far, this one ranks 131 (worst first). The others scored between 0 and 41.
17.5points earned
/
79points we could see (79%)
=
22.2%provision
×
1exposure — local
=
22.2provision × exposure
→
22SSI · rounded to nearest · v0.3

Only what the imagery could actually resolve is scored (79% of the rubric here); the rest is left uncounted rather than guessed. A road with full protective infrastructure scores near 100.

The road in context · derived from public data

Where this road sits

Before the checks: what kind of road this is, how it meets other roads, and what passes it. These lines describe the road and its surroundings — they do not change the score.

Road layout around the gate, drawn from OpenStreetMap
Road layout · drawn from OpenStreetMap · blue dot = school coordinate
FrontageThe gate opens onto a local street, on its W side
Junctionthe gate area sits at a 3-leg junction
Street activityno bus stop or shops mapped within 150 m (OpenStreetMap)
Crash recordcrash-location data is not yet available for Delhi — this line will be added when a public source lands
Exposure contextLow — 17/100 (partial: no crash component yet). Describes how much traffic and crash risk passes this road — context only, never part of the road score (method: exposure v1, Data page)

Road layout data © OpenStreetMap contributors (ODbL), retrieved 13 Aug 2026 · crash data: Jaipur Police · derivations: `exposure_v1` on the Data page.

What we found · five checks · IRC:SP:32-2023

Five things we checked — and the photo behind each

Each check was read once, then verified blind by a second reader on a separate account. The photo each finding came from sits right beside it. Tap “see how this was judged” for the full reasoning.

✕
Slowing traffic downP1 · Physical speed control

Nothing slows traffic at the gate

No speed hump, table or rumble strip on the approach — vehicles reach the gate at full speed.

Absent
Also cited for this check
0 of 30 points
LevelNone (L0)
Points0 of 30
ConfidenceHigh
Coverage seen≈85%
VerificationConfirmed — both readers agreed
The full reasoning

No physical speed-control devices anywhere in the zone: no hump, table, rumble strip or transverse bar markings on either approach or at the gate. Road surface is plain asphalt in all frontage views.

✕
Getting across the roadP2 · Safe crossing

No safe place to cross

No marked or raised pedestrian crossing at or near the gate.

Absent
Also cited for this check
0 of 25 points
LevelNone (L0)
Points0 of 25
ConfidenceHigh
Coverage seen≈85%
VerificationConfirmed — both readers agreed
The full reasoning

No marked pedestrian crossing of any kind in the zone (no zebra, no faded remnant, no refuge). Carriageway is unmarked in all frontage and gate-approach views.

◑
Walking without stepping into trafficP3 · Footpath & separation

A footpath on one side

A continuous, usable walking edge runs along one side.

Partial
Also cited for this check
12.5 of 25 points
LevelBasic (L2)
Points12.5 of 25
ConfidenceHigh
Coverage seen≈75%
VerificationConfirmed — both readers agreed
The full reasoning

Local-street standard applied. A paver-block walkable edge runs fairly continuously along one side over the observed frontage (JlbYIKhZxhcQ, 2cJ6l72gWoC1, BuQ0jkdYDKSe). The opposite side and some stretches are unpaved earthen shoulder, and the edge directly at the gate is earthen; both-side continuity is not established, so L2 (continuous usable one side) rather than L3. Assessment excludes parked scooters (momentary).

✕
Being seen and expectedP4 · Signage & zone identity

No school-zone signs

Drivers get no warning that a school gate is here.

Absent
Also cited for this check
0 of 10 points
LevelNone (L0)
Points0 of 10
ConfidenceHigh
Coverage seen≈70%
VerificationConfirmed — both readers agreed
The full reasoning

No school-warning signs on either approach, no speed-limit sign or carriageway speed stamp, and no 2023-identity zone assets. The only signage near the gate is a red 'trespassing prohibited' compound-security board, which is not a school-zone asset.

◑
The gate itselfP5 · Gate environment

Space and a railing at the gate

A clear setback or railing gives room to gather off the carriageway.

Partial⟳ Corrected in review
MinimalBasic

An independent second reader changed this — the two readings disagreed, and the evidence below settled it.

Also cited for this check
5 of 10 points
LevelBasic (L2)
Points5 of 10
ConfidenceMed
Coverage seen≈65%
VerificationCorrected in the second reading
The full reasoning

The two reads differ (audit L1 'minimal setback / informal dirt verge' vs blind L2 'clear setback giving off-carriageway assembly space'); the deciding image is lK4GVhvxFTr7_h162_f90_gate_wide (with _f35_gate_zoom and the adjacent frontage views). It shows the blue gate recessed in the compound wall behind a broad, consistently present earthen shoulder that separates the gate from the traffic lane by several metres, providing genuine off-carriageway assembly space before the carriageway. This is more than the 'minimal setback' of L1. Assessing built form only, the audit's L1 fell: it treated the wide setback as a mere informal verge, undervaluing the clear off-carriageway space that the wall/gate position affords. No separate pedestrian opening (single vehicle gate) and no continuous rail gate-to-crossing, so L3 is not reached; no marked pick-up/drop-off bay, so not L4. Final L2 at MED confidence (assessed essentially from the single gate location; L2 does not require HIGH). The parked two-wheelers on the apron are momentary and excluded.

At the gate
On the frontage road
Along the street
Some captures sit on neighbouring lanes; older ones are shown greyed and were used only for context.
What must be fixed · 5 actions

What would make this road safe — and who owns each fix

Each action maps to a failing check, the relevant IRC:SP:32-2023 clause, and the responsible agency. Agency labels are provisional and correctable through the dispute channel.

01Lifts P1

Install a speed table or twin speed humps within 30 m of the gate

IRC:SP:32-2023 §5.13 · Table 5.1MCD / PWD · provisional

Speed humps near schools roughly halve child-pedestrian injury odds (Tester 2004); 30 km/h calmed zones ≈ 40% fewer casualties (Grundy 2009).

02Lifts P2

Mark a crossing within 20 m of the gate — table-top preferred

IRC:SP:32-2023 §5.4.3MCD / PWD · provisional

Raised crossings cut vehicle speeds at the exact conflict point.

03Lifts P3

Provide a continuous clear walking edge on the school side

IRC:SP:32-2023 §5.4.1MCD / PWD · provisional

A continuous footpath keeps children off the carriageway on the approach, not only at the gate.

04Lifts P4

School-zone warning signs on both approaches with the speed limit

IRC:SP:32-2023 §5.8MCD / PWD · provisional

The zone must announce itself to drivers before the gate.

05Lifts P5

Add space and a marked pick-up bay off the carriageway at the gate

IRC:SP:32-2023 §5.2MCD / PWD · provisional

Children should not step from the gate into a moving traffic lane.

Responsible-agency labels come from the CFI field instrument’s mapping and are correctable via the dispute channel.

Re-audit timeline

2026-09-04Audited
2027-03-07Re-audit due

Every published road is re-read every six months, or as soon as new Street View imagery lands, or on a sustained dispute.

Something wrong on this page?

The entrance, the imagery, a finding — if any of it is wrong, tell us. A dispute pauses this page while the audit is re-verified, and the correction is logged in the public record.

Dispute this audit