From the Transportation edition of November 10, 2026
After two Punggol AV near misses, LTA also paused Grab's junction testing, and residents voiced concern but backed continued trials
Land Transport Authority, Singapore (reported by CNA) · Transit; autonomous shuttles; roadway safety · Punggol, Singapore
- Publisher
- CNA
- Original publication
- 09 Nov 2026 08:22PM SGT (updated 10 Nov 2026)
- Source retrieved
- 2026-11-11
- Event date
- 2026-11-05
What happened
CNA reports two Nov. 5 near misses in Punggol: a Grab AV came close to a girl crossing during a discretionary left turn, and a ComfortDelGro AV turned into an oncoming vehicle while attempting a U-turn. Both vehicles were testing new routes for on-demand services, not their fixed shuttle routes. LTA is investigating, directed Grab to pause testing at such junctions and told ComfortDelGro to pause U-turns at the junction. Fifteen passenger AVs operated in Punggol as of Nov. 3. Of 12 residents interviewed, parents were most concerned, but most supported trials continuing.
Why it matters
Extends the archived LTA ComfortDelGro pause with the Grab pause and resident sentiment. Relevant to U.S. transit agencies piloting AV shuttles: incidents clustered when vehicles moved off fixed routes into new on-demand paths, and targeted pauses preserved public support.
Evidence and measured results
News reporting with resident interviews (12 people, not a representative sample) and official actions. No investigation findings yet.
Limitations and uncertainty
Overlaps an archived item on the ComfortDelGro pause; new content is the Grab pause, operating context and resident views. Interview sample is small and self-selected; non-U.S. context.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-10; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- AV shuttle pilots can lose public support after near misses during service expansion.
- Stakeholders
- Transit innovation lead
- Regulator or permitting office
- Community engagement manager
- Operator safety lead
- Discovery questions
- What gates apply before an AV route or maneuver is added?
- Who can impose targeted pauses?
- How are incidents communicated to residents?
- Value hypothesis
- Route-expansion gates and incident playbooks may preserve pilot continuity; no safety results are evidenced.
- Potential engagement
- Design of AV pilot expansion criteria and incident communication playbook.
- Unsupported claims
- AV safety performance
- Representative public opinion
- Cause of the near misses
Pre-sales engineering
Role takeaway
- Fit
- Fits agencies running or permitting AV shuttle or on-demand pilots.
- Architecture and integration
- Treat new routes and maneuvers as changes to the operating domain requiring validation.
- Prerequisites
- Scenario library for unprotected turns and crossings
- Incident data capture
- Operator reporting obligations
- Constraints
- Investigations still open
- Non-U.S. regulatory context
- No technical incident detail
- Security
- Govern use of public dashcam and onboard video in investigations.
- Proof of value
- Scenario tests before each new route
- Measured safety-driver interventions
- Near-miss reporting rate
Delivery
Role takeaway
- Work
- Implement expansion gates, targeted pause procedures and public updates.
- Dependencies
- Regulator authority
- Operator data sharing
- Community channels
- Ownership
- Transit agency or regulator overseeing the pilot.
- Skills and adoption
- Train staff to review AV incident data and run community briefings.
- Governance checkpoints
- Pre-expansion safety review
- Post-incident investigation
- Resume decision criteria
- Acceptance criteria
- Scenario tests completed before expansion
- Public update within an agreed time after incidents
- Pause and resume decisions documented
- Risks
- Expansion outpaces validation
- Incidents near schools
- Loss of community trust
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Not addressed beyond the distinction between fixed-route shuttles and on-demand route testing.
Governance
Who approves, reviews and stays accountable for outcomes?
Regulator used scenario-specific pauses (junction types, U-turns) rather than halting the program, pending investigation.
Security and privacy
What data, permissions and controls need testing?
No security or privacy content; incident evidence came from public dashcam and social media videos.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Parents with young children express avoidance behavior; no accessibility analysis.
Procurement
What should contracts, pricing and exit terms secure?
Not addressed.
Operating model
Which teams own the service once it runs?
Expansion from fixed routes to on-demand testing changed the risk profile, prompting targeted operational restrictions.
Publication history
- 2026-11-10Transportation · Issue 136 resources
Stable resource ID: punggol-residents-av-near-misses-lta-pauses-grab-junction-testing-2026-11-09