School Bus Incident IoT Log

This dataset provides comprehensive, real-time logs of school bus incidents detected by edge IoT sensors, including event type, location, severity, and contextual information such as bus, route, and driver. It enables K-12 transportation teams to monitor fleet safety, ensure compliance, and respond rapidly to critical events, supporting data-driven improvements in student transportation operations.

  • last updated 1 Jan 2026
  • by GoMask
The brief that made it

Real-time fleet safety monitoring and incident response

Sample rows

preview · 8 of 62 rows · all 19 columns
incident_idstringevent_severitystringspeed_kphfloatvideo_availablebooleanresolved_by_user_idstringbus_idstringroute_idstringschool_district_idstringevent_timestampdatetimeevent_typestringsensor_idstringlatitudefloatlongitudefloatstudent_countintegerdriver_idstringaudio_availablebooleanincident_descriptionstringresolvedbooleanresolution_timestampdatetime
A7C3F0D2info0trueUSR-JSMITHBUS-0192RT-102ASD-ALPHA2024-05-01T07:15:22Zdoor_openSNS-001542.3721-71.113223DRV-104falseNormal pickup. Door opened at school.true2024-05-01T07:30:01Z
B2E1-9F6Dinfo0falseUSR-ABROWNBUS-0025RT-210BSD-BETA2024-05-01T14:55:11ZidleSNS-009942.4058-71.028415DRV-097falseBus idling at final stop.true2024-05-01T15:05:14Z
7A4B-11C8warning32.4trueblankBUS-0037RT-318ESD-GAMMA2024-05-02T08:22:47Zhard_brakeSNS-020242.329-71.049718DRV-083trueHard brake to avoid cyclist.falseblank
F6C1B8A2critical54.9trueblankBUS-0113RT-102ASD-ALPHA2024-05-01T07:18:39ZspeedingSNS-013442.3715-71.114820DRV-104trueBus exceeded speed limit in residential zone.falseblank
1C-8F7B-DAinfo0falseUSR-NSCOTTBUS-0056RT-154CSD-DELTA2024-05-01T16:04:50Zdoor_closeSNS-004542.3603-71.05886DRV-119falseDoor closed after student dropoff.true2024-05-01T16:10:22Z
E9983F4Binfo17.2falseUSR-JSMITHBUS-0192RT-102ASD-ALPHA2024-05-02T07:11:12Zgeofence_entrySNS-001542.3744-71.119825DRV-104falseBus entered school geofence.true2024-05-02T07:19:00Z
D1F6E5C3critical12.1trueblankBUS-0245RT-322BSD-BETA2024-05-03T13:44:33Zcollision_detectedSNS-021342.4045-71.062330DRV-121trueMinor collision with parked car.falseblank
4B3A-7E9Fwarning0trueUSR-JSMITHBUS-0113RT-102ASD-ALPHA2024-05-02T07:25:11Zstop_arm_deployedSNS-013442.3727-71.116921DRV-104falseStop arm deployed for student crossing.true2024-05-02T07:29:01Z

What the 62 rows show

from the 62-row sample

Info (event severity) stands out: mean speed_kph is 5.7, against 31.2 for the rest.

  • 45%video_available = true
  • 6.4median speed_kph
  • 11event types
  • 14school districts
  • 15routes
  • 15drivers
Mean speed_kph by event_severity62 rows
020405.7info33 rows29.4warning21 rows36.0critical8 rows
speed_kph62 rows, in bands of 10
0204032667361104080speed_kph →

Median 6.4, from 0.0 to 75.5.

resolved_by_user_id36 rows with a value · 26 left blank
  1. USR-JSMITH8
  2. USR-ABROWN4
  3. USR-KLEE4
  4. USR-7814
  5. USR-NSCOTT3
  6. USR-8033
  7. USR-9083
  8. USR-8122
  9. USR-9451
  10. USR-7101
19 columns by typefrom the column list below
  • string 10
  • integer 1
  • float 3
  • datetime 2
  • boolean 3

Columns

19 columns in four groups
blueprint · 19 columns
columntypedescriptionexample
Text 10 columns
incident_idstringUnique identifier for each bus incident log entryuniqueA7C3F0D2
bus_idstringUnique identifier for the school bus involved in the incidentBUS-0192
route_idstringIdentifier for the bus route associated with the incidentoptionalRT-102A
school_district_idstringIdentifier for the school district operating the busoptionalSD-ALPHA
event_typestringType of incident or event detected (e.g., hard_brake, door_open, speeding, idle, geofence_exit, etc.)11 valuesdoor_open
event_severitystringSeverity level of the incident (e.g., info, warning, critical)info · warning · critical · optionalinfo
sensor_idstringUnique identifier for the IoT sensor that captured the eventSNS-0015
driver_idstringIdentifier for the bus driver at the time of the incidentoptionalDRV-104
incident_descriptionstringFree-text description or notes about the incidentoptionalBus entered geofence.
resolved_by_user_idstringIdentifier for the user or staff member who resolved the incidentoptionalUSR-JSMITH
Numbers 4 columns
latitudefloatLatitude coordinate where the incident occurred-90 to 9042.3721
longitudefloatLongitude coordinate where the incident occurred-180 to 180-71.1132
speed_kphfloatBus speed in kilometers per hour at the time of the incident0 or more · optional0
student_countintegerNumber of students on board at the time of the incident, if available0 or more · optional23
Dates and times 2 columns
event_timestampdatetimeDate and time when the incident was detected by the IoT sensor2024-05-01T07:15:22Z
resolution_timestampdatetimeDate and time when the incident was marked as resolvedoptional2024-05-01T07:30:01Z
True or false 3 columns
video_availablebooleanIndicates if video footage is available for the incidentoptionaltrue
audio_availablebooleanIndicates if audio recording is available for the incidentoptionalfalse
resolvedbooleanIndicates if the incident has been reviewed and resolvedoptionaltrue

Use it for

  • video available45%28 of 62 rowsmean speed kph by eve…5.7info29.4warning36.0critic…

    An education dashboard

    The video_available rate, speed_kph by event_severity and a breakdown of resolved_by_user_id. Excel, Power BI or Tableau.

  • Why do the 33 info rows have a mean speed_kph of 5.7?

    A root-cause class exercise

    Hand out the rows and one question. The answer is in the data, not in the brief.

  • A software demo

    Believable incidents with bus_id, route_id and school_district_id to fill a screen in front of a buyer.

Not quite right?

Make it yours.

Same 19 columns, your size and your rules. See 20 rows before you pay.

Preview 20 rows free

1,000 rows: $1.99 · 10,000: $12.99One-time. No subscription. All prices

This dataset62 rows19 columns
Yours1,000 rows19 columns

blueprint · school-bus-incident-iot-log

Behind this dataset

Same schema. As many rows as you need.

These 62 rows came out of a blueprint — 19 columns with generation rules behind each one. Open it in Data Factory to retune a column, add your own, wire in foreign keys, and run it at the size you actually need.

Rules it was built with
  • Each log entry must contain timestamp, sensor ID, and bus route identifier.
  • Incident types must be categorized (e.g., door left open, speed anomaly, unauthorized stop).
  • Severity level assigned based on sensor readings and predefined thresholds.
  • Compliance status (resolved/unresolved) must be logged within 24 hours.
  • GPS coordinates are required for all incident events.
Rows
Open the blueprint in Data Factory

1 credit per row. New accounts start with 25 free credits.

Exports
CSV, JSON, JSONL, Parquet, SQL, Excel, TSV, XML
Licence
yours to use, including commercially
API slug
school-bus-incident-iot-log

What should your data show?

Preview 20 rows free
No signup. No card.