FirstAlerts
Plane CrashesVersion 2

One Dead, One Seriously Injured in Piper PA-32-260 Accident Near Rio Linda, California

The accident record lists two people on board the single-engine Piper on December 24, 2025; the National Transportation Safety Board is investigating and the cause has not been determined.

By AI ReporterUpdated Aug 7, 2026, 10:03 a.m. ET
One person was killed and one was seriously injured when a single-engine was involved in an accident near Rio Linda, California, on December 24, 2025, at about 8:30 p.m. local time, according to the accident record. The investigation is at an early stage and details are still developing. The accident record lists people on board, one fatality and one serious injury. It states the aircraft sustained substantial damage and classifies the flight as a Part 91 general aviation flight. The National Transportation Safety Board is investigating. The cause has not been determined. The accident record identifies the aircraft as a registered . Aircraft registry records list the type as a with a Lycoming 0-540 series engine, serial number 32-688, registered in the United States, and give the registered owner as A&R Aero LLC; the owner of record is not necessarily the operator, the pilot, or otherwise connected to the flight. California Secretary of State filings, as reproduced by BizProfile and OpenCorporates, show A&R Aero LLC as an active, manager-managed California limited liability company formed on 17 February 2017 (document number 201706010120), with a principal address in Sacramento. Those filings list Ammar Nazir as chief executive officer, manager and registered agent, and Jay Hemanshu Vyas as a manager; the investigation has made no finding connecting either of them to this accident. Registry data reproduced by FlightAware shows the company as owner of , a 1966 . Related entities registered at the same address include AR Aero Services LLC, formed 13 September 2022 and described in registry data as aviation services and rental, and AR Airplane LLC, formed 18 March 2025. No source found establishes an airport or operating base for the company. This background concerns the owner of record only and says nothing about what happened. As a matter of record, the NTSB database, which begins in 2008, contains 42 other cases involving the , of which 16 involved a fatality. That count is not a safety rate and says nothing about the cause of this accident. Geographic reference data places Rio Linda in Sacramento County, California, with a settlement elevation of 52 feet, and lists Rio Linda Airport (L36) 1. miles to the northwest and McClellan Airfield (KMCC) 3.4 miles to the west-northwest; those bearings describe the town, not the accident site. A weather observation recorded at McClellan Airfield, 3.4 miles away and 25 minutes from the reported time of the accident, showed wind from 150 degrees at 19 knots, visibility 10 statute miles, few clouds at 6,500 feet and a temperature of 57°F. That is an instrument reading and is not a stated cause or contributing factor. The investigation remains open.

Was this report accurate and useful?

Reference data

From aircraft and geographic registries, not from the news sources. Registry records can be out of date, and describe the aircraft and the place only — they say nothing about what happened.

Registration
N2785Q
Type
Piper PA-32-260
Engines
LYCOMING 0-540 SERIES
Registered owner
A&r Aero LlcThe owner of record is not necessarily the operator, the pilot, or otherwise connected to the flight.
Terrain elevation
52 ft
Nearest aerodrome
1.2 miles NW of Rio Linda Airport (L36)

Sources

Revision history

  1. Version 27 Aug 2026, 14:03current

    Corrected the direction of the nearby aerodromes to match the geographic reference data, clarified those bearings describe the town rather than the accident site, and added that the investigation remains open.

  2. Version 15 Aug 2026, 19:00

    First published.

How we work

This site models an investigative reporter rather than a wire desk. The aim is the most complete, accurate and timely account we can assemble — all three, not a trade between them. Reports go out within minutes of the coverage they are built from, carrying context a newsroom would otherwise need a day and a records request to gather: what has happened at this place before, what the operator’s record is, which aircraft it actually was.

Reports are built from primary sources — accident and court records, official registries, weather observations, agency statements — and from reputable news organisations, each named where their reporting is used. Facts are extracted before anything is written, and every one must be supported by a quotation found in the source itself; the model that writes the report is given only those verified facts and never sees the article, so it cannot introduce a detail no source stated.

Where sources disagree we publish the disagreement, attributed, rather than picking a figure. Where a fact comes from a record rather than a reporter, we say so, and the language matches: an instrument reading is never described as something anyone confirmed. Some things are deliberately withheld — a suspect is not named until an agency names them on the record, victims until families or officials release them — and corrections appear as visible revisions, never as silent edits.

None of that makes a report true. A quotation check proves a source said something, not that it was right, and an automated system can be confidently wrong in ways the checks do not catch. If something here is wrong, the feedback above is how it gets found. The full methodology, including what we refuse to publish.