Frequently Asked Questions

Bincident is a public incident intelligence platform focused on aviation safety events. It combines timeline context, aircraft and operator data, weather notes, and occupant outcomes so incidents can be reviewed quickly and consistently.

Some investigations are still open when an incident is first published. In those cases, we show verified data that is available at the time and continue updating records when official agencies release additional findings.

Bincident aggregates data from official investigation authorities, regulator releases, airport and operator statements, and verified public reporting. We prioritize primary sources and preserve references for traceability.

Records are updated as soon as reliable new information is available. Major updates usually follow formal reports, while smaller corrections can happen continuously when better source material is found.

We cross-check source claims, keep references attached to affected fields, and avoid speculative details. If information is uncertain, the UI reflects that instead of presenting unverified certainty.

Severity is based on the most severe confirmed outcome in the event. Fatal outcomes are prioritized above injuries, and injuries are prioritized above no-injury events. This keeps categorization deterministic across all incidents.

Bincident includes safety-relevant aviation events with credible documentation and sufficient context to present meaningful detail. Routine operational noise without safety relevance is generally excluded.

References are scoped by section so you can validate individual claims directly where they appear. This keeps aircraft, operator, weather, and occupant information auditable without mixing unrelated sources.

Map support may be temporarily disabled while underlying data or rendering behavior is being revised. During that time, detail sections continue to provide the complete textual and referenced incident context.