TASAS and location records
Request all TASAS records for the specific postmile location and a reasonable surrounding radius, covering at least five years before the incident, so the agency cannot rely on a narrow or outdated slice of data.
Caltrans Warning Signs California Litigation: Obtaining the Records That Prove Notice
Caltrans maintains extensive internal records documenting known roadway hazards, prior accident history, and maintenance decisions across the state highway system, and these records are frequently the single most decisive evidence in a failure-to-warn case. Effective Caltrans warning signs California litigation strategy centers on identifying, requesting, and using these records before the agency's litigation position hardens around a no-notice defense.
5+ years
Records span to request preceding an incident
1-2 years
How far the TASAS database can lag real-world crashes
Understanding TASAS and Its Limitations
Caltrans's primary internal accident-tracking tool is the Traffic Accident Surveillance and Analysis System, commonly referred to as TASAS. This database compiles reported collision data by location to help the agency identify high-accident locations warranting engineering review. Counsel should request TASAS data early, but should also anticipate a critical limitation: TASAS data can lag actual, real-world accident occurrence by a year or more due to reporting and processing delays. An agency that points only to TASAS data showing no qualifying accident history at a given location, without addressing whether more current data existed elsewhere within the agency or through the California Highway Patrol, has not established a complete absence of notice, only an absence of notice within a database known to be outdated.
Internal Hazard Reports and Maintenance Records
Beyond TASAS, Caltrans district offices generate a range of internal reports, memoranda, and maintenance records that can independently establish notice of a hazardous condition. These include district traffic investigation reports, safety review memoranda prepared in response to citizen complaints or field observations, maintenance supervisor logs and diagrams, and internal correspondence discussing proposed signage or engineering changes at specific locations. These records are frequently more current and more specific than TASAS data, and they often exist in district office files rather than centralized statewide databases, meaning a request limited to headquarters records can miss the most damaging evidence entirely.
Structuring Discovery Requests for Maximum Yield
District reports and correspondence
Request district-level traffic investigation reports, safety review memoranda, hazard assessments, and any internal or public correspondence raising safety concerns about the location, along with records of any committee review of signage or design.
Maintenance records without a label filter
Request maintenance logs, diagrams, and photographs referencing the location without limiting the request to documents labeled "hazard," because critical notice evidence can appear in informal documentation such as a supervisor's hand-annotated diagram.
Why This Evidence Drives Liability and Damages
A jury responds very differently to a single missing sign than to a decade of internal reports, multiple prior crashes, and a maintenance employee's own handwritten acknowledgment of the danger. The volume and specificity of documented internal notice transforms a case from a debatable liability dispute into a clear demonstration of institutional indifference, affecting both the liability finding and the damages assessment. Depositions of the district traffic engineer and any maintenance supervisor with direct knowledge of the location are essential to authenticate and explain these documents.
Theory pleaded
Jury finding
Primary agency database
TASAS, useful but often outdated by a year or more
Most decisive records
District reports and hand-annotated maintenance diagrams
Key witnesses to depose
District traffic engineer and maintenance supervisor
Effect on the jury
Documented notice reframes the case as institutional indifference
The case behind this page
A $14.1 million verdict built on a decade of agency records
Six prior crashes, internal hazard reports from 2001 through 2005, and a supervisor's diagram marked with a reference to multiple deaths.
Read the full caseRelated defense
Government Code 830.8 warning signs immunity and its limits
How the trap door exception makes a failure-to-warn case actionable even when the agency raises sign immunity.
See where the immunity failsKeep Reading
Related breakdowns from this case and our dangerous roadway practice.
Referring a case against Caltrans or a public agency?
We take dangerous roadway and failure-to-warn cases against public entities as counsel or co-counsel and pay statutory referral fees.
Refer a caseFrequently Asked Questions
What is TASAS and why does it matter in a Caltrans case?
TASAS, the Traffic Accident Surveillance and Analysis System, is Caltrans's internal database tracking collision history by location. It matters because agencies often rely on it to argue a lack of notice, but the database can lag real-world accident data by a year or more, limiting its reliability as a complete notice record.
What records besides TASAS should be requested from Caltrans?
District-level traffic investigation reports, safety review memoranda, maintenance logs and diagrams, internal or public correspondence raising safety concerns, and records of any engineering committee review of the location, regardless of whether it resulted in a change.
Why are maintenance records important even if they do not use the word hazard?
Critical notice evidence sometimes appears in informal documentation, such as a maintenance supervisor's hand-annotated diagram, rather than in a formally labeled hazard report, so discovery requests should not be limited to documents using specific hazard terminology.