Overall Trends
Total, fatal, and serious accidents in the selected range.
Premium research interface
The modern interface for aviation safety intelligence.
Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.
63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Search everything
Fast key and full-text search with live filters, watches, and precise metadata.
Use quotes for exact phrase matches (for example "fuel selector valve").
Featured Report
Safety trends by operating rule
Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.
Loading trend charts…
High-signal investigations
Major cases, deep-report coverage, and investigation media across decades of NTSB history.
Browse the aviation graph
Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.
Last Data Update
By Decade
By Month
Aircraft Manufacturer
More manufacturersAirports
More airportsOperators
More operatorsAbout
Aviation safety reports, made easier to study
NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.
The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.
The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.
FAQs
NTSB Report
April 27, 2012
Las Vegas, NV
Overview
Report Status
Final with probable cause
Event Type
Incident
Date
April 27, 2012
Location
Las Vegas, NV
NTSB Number
OPS12IA535
The flight crew of an Airbus A320, operated by an air carrier, was conducting a visual approach to runway 25L while a Learjet 60 (LR60) was simultaneously cleared for takeoff from runway 19L. The pilot of the A320 elected to execute a go-around and came into hazardous proximity with the LR60 as it departed runway 19L. After the pilot of the A320 executed the go-around, neither local controller was able to provide control instructions to separate the two aircraft. The closest proximity of the two aircraft was approximately 0.3 nautical miles laterally and 100 feet vertically. The two aircraft were being controlled by different tower controllers, who were simultaneously routing aircraft to land on runway 25L and to depart from runway 19L--nonintersecting, converging runways whose flight paths intersect. This procedure was not prohibited by the Federal Aviation Administration (FAA), and there were no FAA-prescribed separation minima or procedures for air traffic controllers to follow when conducting simultaneous independent converging runway operations in the event a pilot elected to execute a go-around. This resulted in the aircraft going around coming into close proximity with the departure aircraft where the flight paths intersected.
NTSB Probable Cause
Federal Aviation Administration procedures that do not ensure separation in the event of a go-around during simultaneous independent runway operations on runways that do not physically intersect but whose flight paths intersect.
Full Narrative
On April 26, 2012, at 1225, two aircraft came within hazardous proximity of one another at McCarran International Airport (LAS), Las Vegas, Nevada, when JBU483, an Airbus Industries A320 arriving at LAS from General Edward Lawrence Logan International Airport (BOS), Boston, Massachusetts, initiated a go around from runway 25L and came into hazardous proximity of XARAV, a Mexican-registered Bombardier Lear Jet 60 (LR60) departing runway 19L. JBU483 made an evasive turn to the left and XARAV initiated a rapid climb. The aircraft came within 0.30 nautical miles laterally and 100’ vertically where the runway flight paths intersected off the departure ends of runway 19L and runway 25L. Both aircraft were under control of two different LAS ATCT local controllers at the time of the incident. There was no damage reported to either aircraft, or any injuries to passengers or crew. JBU483 was an Airbus Industries A320 scheduled 14 Code of Federal Regulations Part 121 passenger flight operating from Boston Logan International Airport to Las Vegas, Nevada. The flight was on a visual approach to runway 25L at Las Vegas McCarran International Airport. XARAV was a non-scheduled 14 Code of Federal Regulations Part 91 personal flight operating from Las Vegas McCarran International Airport. For further information, see the Air Traffic Control Group Chairman's Report in the docket for this case.
Flight
Event TypeIncident
Event Time11:25 PDT
Nearest Airport0nm
Flight Plan FiledIFR
Aircraft FireNo
Aircraft ExplosionNo
Aircraft
Operating RulePart 121
People & Injuries
Fatal0
Serious0
Minor0
Uninjured0
Total0
Conditions
ConditionsVMC
LightDaylight
Wind180° @ 19 kt, gusting 26 kt
Visibility10 sm
CeilingBroken clouds 9500 ft
Temperature / Dew Point68 F / 46
Altimeter29.77 inHg
Observation Time17:56
Weather SourceWFAC