Private jet skids off runway at Las Vegas airport
Summarised from 2 outlets · Updated 19 Oct, 08:56 · Archive
A private jet skidded off a runway at Harry Reid International Airport in Las Vegas on Sunday morning, hitting a perimeter fence.
A Dassault Falcon 50 aborted its takeoff and skidded off Runway 1L at Harry Reid International Airport in Las Vegas at approximately 11 a.m. on Sunday. The aircraft made contact with the airport's perimeter fence. There were no reported injuries.
The jet was scheduled to depart for Toronto's Pearson International Airport. According to flight-tracking data, the plane moved slowly from its taxi position onto the runway before continuing past the end of the pavement, veering to the right and coming to a stop. Officials have not disclosed what triggered the aircraft to leave the tarmac.
Both Runway 1L and Runway 1R were closed for safety inspections following the incident. The Federal Aviation Administration issued a ground stop for the airport, citing an aircraft emergency. This closure caused delays of more than an hour for approximately 360 flights before the FAA lifted the measure by Sunday evening. Airport officials urged travellers to check with their airlines about flight status.

How it is being reported
- Private jet crashes into fence at Las Vegas airport, triggering chaos for hundreds of flightsOfficials say a private jet went off the end of a runway during a planned takeoff at the main airport in Las Vegas and hit a perimeter fenceIndependent World · 19 Oct, 08:31
- Jet skids off runway after botched takeoff at Las Vegas airportA private jet aborted its takeoff after it ran off the end of a runway at Harry Reid International Airport Sunday morning.New York Post · 18 Oct, 21:30
In this story: Harry Reid International Airport · Las Vegas · Federal Aviation Administration · Toronto Pearson International Airport · Jacks Wings LLC
This summary was written by AI from the headlines and standfirsts above, and states as fact only what at least two outlets report. How we use AI · Report a problem
Comments (0)