About BridgeReport.org

BridgeReport.org was founded with a singular mission: to democratize access to America's bridge infrastructure data. Every day, over 178 million trips are taken across the nation's 623,000+ highway bridges. Yet despite the critical role these structures play in our daily lives, detailed information about their condition, age, and structural integrity has historically been locked away in technical databases accessible only to engineers and government officials.

We believe that every American has the right to know the condition of the bridges they cross. Parents driving their children to school, commuters heading to work, and truckers transporting goods across the country all deserve easy access to factual, comprehensive bridge safety data. BridgeReport.org transforms complex federal inspection data into clear, actionable information that empowers citizens to make informed decisions and engage meaningfully with their local infrastructure priorities.

Our platform serves multiple audiences: concerned citizens seeking to understand their local bridge conditions, journalists investigating infrastructure stories, researchers studying transportation networks, local government officials benchmarking their bridge inventories, educators teaching about civil engineering, and infrastructure enthusiasts who share our passion for the built environment.

BridgeReport.org is created and maintained by a dedicated team of infrastructure enthusiasts, data scientists, software engineers, and geography experts who share a common passion: understanding and communicating the state of America's built environment. Our diverse backgrounds span civil engineering, urban planning, cartography, data visualization, and public policy.

What unites us is a deep appreciation for the engineering marvels that connect our communities. From the iconic Golden Gate Bridge to the humble county road crossings that serve rural America, every bridge tells a story of human ingenuity, community need, and ongoing stewardship. We are driven by a belief that infrastructure literacy is essential for civic engagement in the 21st century.

Our team members have collectively spent decades studying transportation infrastructure, analyzing government datasets, and building tools that make complex information accessible to general audiences. Several of us have backgrounds in geographic information systems (GIS) and have contributed to open-source mapping projects. Others bring experience from journalism, having covered infrastructure policy and transportation safety for major publications.

We operate as an independent, non-partisan project. BridgeReport.org is not affiliated with any government agency, political organization, construction company, or engineering firm. Our sole agenda is providing accurate, comprehensive, and useful bridge data to the public. We do not advocate for specific policy positions, though we do believe that informed citizens make better decisions about infrastructure investment.

The foundation of BridgeReport.org is the National Bridge Inventory (NBI), a comprehensive database maintained by the Federal Highway Administration (FHWA) within the U.S. Department of Transportation. The NBI contains detailed information on every highway bridge in the United States that spans more than 20 feet, representing over 623,000 structures nationwide.

The National Bridge Inventory has been collected since 1971 following the tragic collapse of the Silver Bridge between West Virginia and Ohio in 1967, which claimed 46 lives. In response, Congress mandated the creation of the National Bridge Inspection Standards (NBIS), requiring regular inspection of all public highway bridges. Today, each bridge must be inspected at least once every 24 months by qualified inspectors, with more frequent inspections required for bridges in poor condition or with special structural concerns.

The NBI data we present includes information on bridge location (latitude, longitude, state, county, and city), physical characteristics (length, width, number of lanes, material type, and design), age and construction history (year built and year of major reconstruction), ownership (state, county, city, federal, or private), traffic data (average daily traffic counts), and most importantly, condition ratings for the deck, superstructure, substructure, and culvert components.

We supplement NBI data with geographic information from the U.S. Census Bureau, including official place names, FIPS codes, and population data. This allows us to provide context about the communities each bridge serves and to organize our data in ways that align with how people think about places.

Additionally, we incorporate historical bridge data spanning multiple years (2020-2024) to track condition trends over time. This multi-year analysis allows users to see whether bridges are improving, stable, or declining in condition—information that single-year snapshots cannot provide.

Data Processing Pipeline

Our data processing pipeline begins with the annual NBI data release from the FHWA, typically published each spring for the previous calendar year. We download the complete dataset, which contains over 120 data fields for each bridge, and process it through a series of validation, cleaning, and transformation steps.

During validation, we check for data anomalies such as impossible geographic coordinates, future construction dates, or condition ratings outside the valid 0-9 scale. We flag but do not alter these records, as anomalies in the source data may reflect genuine reporting issues that users should be aware of. Our processing logs track all flagged records for transparency.

Data transformation involves converting raw NBI codes into human-readable descriptions. For example, material code "1" becomes "Concrete," owner code "01" becomes "State Highway Agency," and historical significance code "1" becomes "Bridge is on the National Register of Historic Places." We maintain comprehensive lookup tables based on the official FHWA Recording and Coding Guide.

Condition Classification

Bridge conditions on BridgeReport.org are classified as Good, Fair, or Poor based on the FHWA's official methodology. This classification uses the lowest rating among the deck, superstructure, and substructure components (or the culvert rating for culvert-type structures).

The condition scale works as follows: Ratings of 7, 8, or 9 indicate Good condition, meaning the component is functioning as designed with minimal deterioration. Ratings of 5 or 6 indicate Fair condition, showing some deterioration but remaining fully functional. Ratings of 4 or below indicate Poor condition, with significant deterioration requiring maintenance attention or potential load restrictions.

It is critically important to understand that "Poor" condition does not mean "unsafe." Bridges in poor condition are still safe for public use—they are inspected more frequently and may have load restrictions or other operational limitations in place. State and local transportation agencies actively monitor all poor-condition bridges and take appropriate action when safety concerns arise. A bridge is closed or restricted long before it becomes dangerous.

Structurally Deficient Classification

We also track the "structurally deficient" classification, which the FHWA defines as any bridge with a condition rating of 4 or below for deck, superstructure, substructure, or culvert. This classification was historically used as a primary measure of bridge condition but has been supplemented by the Good/Fair/Poor system since 2016. We include both metrics to provide historical continuity and to align with how some government reports still categorize bridges.

Geographic Processing

Each bridge in the NBI includes latitude and longitude coordinates, which we use to place bridges on interactive maps and to associate them with cities, counties, and states. However, the NBI's place codes (FIPS place codes) sometimes refer to Census-Designated Places (CDPs) or unincorporated areas that may not be familiar to users. We process these codes using Census Bureau data to provide the most accurate and recognizable place names possible.

For county-level aggregations, we use the 5-digit FIPS county codes present in the NBI data. For state-level aggregations, we use the 2-digit FIPS state codes. All percentages and statistics are calculated from the underlying bridge records, not from secondary sources, ensuring consistency across our platform.

Trend Analysis

Our trend analysis compares bridge conditions across multiple years of NBI data. We track the same bridge over time using its unique Structure Number, which remains constant even if other bridge attributes change. Trends are classified as Improving (condition rating increased), Declining (condition rating decreased), or Stable (no change in condition category).

Aggregate trends for states and the nation are calculated by comparing the percentage of bridges in each condition category year over year. A state with a decreasing percentage of poor-condition bridges is showing improvement, while one with an increasing percentage is experiencing decline.

We believe in complete transparency about what our data can and cannot tell you. Understanding these limitations is essential for using BridgeReport.org effectively.

Inspection Timing: NBI data reflects the condition of each bridge at its most recent inspection, which may have occurred up to 24 months ago (or longer for bridges that qualify for extended inspection intervals). Conditions may have changed since the last inspection due to deterioration, maintenance work, or reconstruction projects.

Data Currency: We process and publish new NBI data as soon as it becomes available, typically in spring each year for the previous calendar year's inspections. The "data year" displayed on each page indicates when the underlying inspection data was collected.

Scope Limitations: The NBI covers highway bridges with spans greater than 20 feet. Smaller bridges, pedestrian bridges (unless they also carry highway traffic), railroad bridges (unless they also carry highway traffic), and private bridges not on public roads are generally not included. Approximately 300,000 additional bridges fall outside the NBI's scope.

Condition vs. Safety: Condition ratings measure the state of deterioration, not the immediate safety risk. A bridge with a poor condition rating may be perfectly safe for normal traffic while awaiting scheduled rehabilitation. Conversely, a bridge could have a sudden safety issue between inspections that wouldn't appear in the data. Always follow posted signs and restrictions.

Geographic Precision: While most NBI coordinates are accurate, some bridges have approximate coordinates or coordinates that place them slightly away from their actual location. We display coordinates as provided in the NBI without modification.

BridgeReport.org is designed to serve multiple use cases, and we encourage users to explore the data in ways that serve their specific needs.

For Concerned Citizens: Use our state and county pages to understand the overall bridge conditions in your area. The "Bridges Near Me" feature lets you find and learn about specific bridges you cross regularly. Remember that poor condition doesn't mean unsafe—but if you have concerns about a specific bridge, contact your state or county department of transportation.

For Journalists and Researchers: Our data can support infrastructure reporting and academic research. We recommend downloading the original NBI data from FHWA for detailed analysis, using our site as a starting point and for geographic context. Please cite both BridgeReport.org and the FHWA National Bridge Inventory when publishing.

For Local Officials: Compare your jurisdiction's bridge conditions to state and national averages. Identify bridges that may need prioritization for inspection, maintenance, or capital improvement programming. Our trend data can help demonstrate progress or identify emerging concerns.

For Educators: BridgeReport.org provides real-world data for teaching about civil engineering, transportation systems, data analysis, and civic infrastructure. Students can explore bridges in their own communities and compare them to bridges elsewhere.

BridgeReport.org is built using modern web technologies chosen for performance, accessibility, and maintainability. Our frontend is built with Next.js, a React framework that enables fast page loads through static generation and server-side rendering. We use TypeScript throughout our codebase to ensure type safety and code quality.

Interactive maps are powered by Leaflet, an open-source JavaScript library, with map tiles from OpenStreetMap contributors. Our data visualizations use D3.js and Recharts for rendering charts and graphs that work across devices and screen sizes.

We process NBI data using Python scripts that validate, transform, and aggregate the raw data into optimized JSON files for web delivery. This preprocessing approach allows us to serve pages quickly without database queries for most page loads.

The site is designed to be accessible and performs well on mobile devices, recognizing that many users will access bridge information while traveling. We follow web accessibility guidelines and test across multiple browsers and devices.

BridgeReport.org is built for the public, and we welcome feedback from our community. If you notice data errors, have suggestions for new features, or want to share how you've used our data, please reach out through our Contact page.

We are particularly interested in hearing from:

• Transportation professionals who can help us improve our data presentation
• Journalists who have used our data in their reporting
• Educators who have incorporated BridgeReport.org into their curriculum
• Local officials who have feedback on how our data compares to their internal records
• Bridge enthusiasts who share our passion for infrastructure

While we cannot respond to every message individually, we read all feedback and use it to guide our ongoing development priorities.

BridgeReport.org would not be possible without the work of countless individuals and organizations dedicated to bridge safety and infrastructure transparency.

We gratefully acknowledge the Federal Highway Administration for maintaining and publicly releasing the National Bridge Inventory data. The bridge inspectors across all 50 states who assess these structures every inspection cycle perform essential work that keeps our transportation network safe.

We also acknowledge the American Society of Civil Engineers (ASCE), whose Infrastructure Report Card has raised public awareness of infrastructure conditions for decades, and the American Road & Transportation Builders Association (ARTBA), whose annual bridge reports provide valuable context for understanding bridge conditions nationally.

The open-source community has provided many of the tools that power BridgeReport.org, including Next.js, React, Leaflet, and countless other libraries. We are grateful for their contributions to the commons.

Finally, we acknowledge the legacy of the Silver Bridge collapse victims, whose tragedy led to the bridge inspection programs that generate the data we present today. Their memory reminds us why infrastructure transparency matters.

BridgeReport.org is an ongoing project, and we have ambitious plans for future development:

• Enhanced Historical Analysis: Deeper trend analysis spanning more years of data, allowing users to see long-term patterns in bridge conditions.
• Improved Search: More powerful search capabilities to find bridges by name, route number, or features crossed.
• API Access: A public API allowing developers and researchers to access our processed data programmatically.
• Additional Data Integration: Incorporation of related datasets such as bridge construction costs, maintenance records where available, and correlation with traffic and safety data.
• Community Features: Ways for users to contribute local knowledge, photos, and historical information about bridges in their communities.

We develop new features based on user feedback and available resources. If you have suggestions for capabilities you'd find valuable, please let us know.