Data source
Data from Kaggle / U.S. DOT, delivered clean.
3 datasets pulled from Kaggle / U.S. DOT's releases, checked field by field and shipped the way you want them — daily, weekly, or hourly, your call.
- 3 datasets
- 1 industry
- Real rows on request
What Datadory delivers from Kaggle / U.S. DOT
32015 Flight Delays and Cancellations (5.8M U.S. Flights)
BTS TranStats - Air Carrier Statistics (T-100) & Airline On-Time Performance
Airline Passenger Satisfaction (103K Survey Responses)
Pick a catch, see the rows.
Name any Kaggle / U.S. DOT dataset and we send real rows from it — not a screenshot of rows. 1,744 datasets. Pick your catch.
Get a sampleAPI, files, or your warehouse. Daily, weekly, or hourly.
Straight answers about Kaggle / U.S. DOT data
What is the Kaggle / U.S. DOT collection?
One cataloged collection filed under Passenger Airlines: the complete U.S. domestic on-time record for calendar 2015, packaged under the U.S. Department of Transportation's own publishing account. It holds 5,819,079 flight-leg rows across 31 columns, joined by a 14-row carrier lookup and a 322-row airport reference.
What time span does the data cover?
January 1 through December 31, 2015 - one closed window, not a rolling feed. Every domestic segment flown that year is present under a single unchanged schema. For months beyond December 2015, pair it with an ongoing on-time series such as the BTS TranStats T-100 collection so history and current operations stay separated.
How is the collection quality-scored?
It scores 9 out of 10 in the Datadory catalog against a 7.81 average, carries a 0.88 community usability rating, and its field documentation verifies clean against the official record layout. More than two hundred public delay-prediction notebooks are built on this exact collection.
Can a sample be cut to specific carriers, routes or months?
Yes. Name the carriers, airport pairs and months you need and the sample arrives in exactly the field shape documented above, so anything prototyped against it survives full delivery intact. The whole year is one consistent schema with no mid-year layout changes to absorb.