Reported collision #29

⚡ Safe Speeds: The map data records a 30 km/h limit, but in the January 2023 photographs a 50 sign stands beside the road and "50" is painted on the carriageway itself — so what the street actually tells drivers is 50, and that discrepancy alone needs resolving. A person on a bike struck at 50 km/h is very unlikely to survive; below about 30 km/h survival becomes far more likely. The road runs in long, gently curving sweeps with generous width and no vertical features, which invites drivers to hold speed rather than shed it. Cutting the posted and actual speed to 30 and backing it up with physical measures — raised crossings that work like speed bumps (speed tables), narrowed entry points, or a build-out at the bend — lowers impact speeds where people cycle in the traffic lane.

🛣️ Safe Roads & Roadsides: The photographs show no cycle lane and no space set aside for bikes; a cyclist must ride in the same lane as cars. Footways are absent or minimal on much of the frontage, and the roadside is lined with hard objects sitting right at the edge — timber utility poles, concrete retaining walls, kerbed planting and metal railings — leaving nowhere safe for someone who wobbles or is squeezed (no clear zone). A large unsurfaced parking area opens onto the road from the east with no defined entrance, so vehicles can cross the carriageway edge almost anywhere. Vegetation and the curve shorten how far ahead a driver can see. A sealed, separated cycle track, or a narrowed carriageway with a protected edge, removes the conflict rather than managing it.

🚗 Safe Vehicles: Automatic emergency braking that detects cyclists, and intelligent speed assistance that holds a car to the posted limit, both reduce the chance of a strike and lower the speed if one happens.

👥 Safe Road Users: The map records no marked crossings or signals here, and none are visible. Clear, consistent speed signing, defined driveway entrances, and speed enforcement would make the intended behaviour obvious from the road itself.