# Incident 20221120021139I: David Weinberg SONEX B, Oakland, CA, November 20, 2022

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: November 20, 2022, 15:12 local time
- Place: Oakland, CA
- Airport: Oakland Airport
- Damage: Minor damage
- Phase of flight: Descent
- Operating rules: General operating rules (Part 91)
- Location: 37.8044° N, 122.2708° W: Placed by OpenAirDocs: center of Oakland, CA, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=37.8044&lon=-122.2708&mi=10
- Aircraft: N5784N, registered now (https://openairdocs.org/aircraft/N5784N) (OpenAirDocs)
- Registry model: David Weinberg SONEX B (registry code 05640EJ, https://openairdocs.org/model/david-weinberg-sonex-b) (OpenAirDocs)
- Registry engine: Ulpower 350I (registry code 62001, https://openairdocs.org/engine/ulpower-350i) (OpenAirDocs)
- Reported make and model: DAVID WEINBERG SONEX B
- Reported engine: ULPOWER 350I
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Private pilot
- Pilot flight hours: 460 total
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20221120021139I

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

AT 2312 ZULU TIME, ^PRIVACY DATA OMITTED^ WAS IN THE AIR FOR APPROXIMATELY 45 MINUTES WHILE PERFORMING AN ENGINE BREAK IN. IT WAS FLYING RIGHT RECTANGULAR PATTERNS AT 1500 FEET MSL.  AN AIRCRAFT WAS ON FINAL FOR RUNWAY 28R AT ROUGHLY 2312 ZULU.  ^PRIVACY DATA OMITTED^ REQUESTED 1000 FEET.  ATC ASKED IF HE WANTED TO COME INBOUND TO LAND, OR IF HE WANTED TO CONTINUE HIS PATTERN AT 1000 FEET.  ^PRIVACY DATA OMITTED^ STATED HE WANTED TO COME INBOUND TO LAND.  ATC INSTRUCTED ^PRIVACY DATA OMITTED^ TO REMAIN AT 1500 FEET FOR THE INBOUND AIRCRAFT.  WHEN ^PRIVACY DATA OMITTED^ WAS OVER THE 28R NUMBERS, ATC INSTRUCTED HIM TO DESCEND TO 1000 FEET AND AVOID TRAFFIC FOR 28R. ^PRIVACY DATA OMITTED^ DID NOT REPLY.  ATC REPEATED THIS TRANSMISSION WITH NO REPLY.  ATC NOTICED ON RADAR THAT HIS TARGET HAD 000 AS HIS ALTITUDE, AND THEN NOTICED ^PRIVACY DATA OMITTED^ WAS IN A RIGHT TUN, ROUGHLY MID-FIELD AND LOW.  ATC INSTRUCTED ^PRIVACY DATA OMITTED^ TO CLIMB, BUT AGAIN RECEIVED NO RESPONSE. THE INBOUND AIRCRAFT WAS ON A VERY SHORT FINAL, JUST OVER THE NUMBERS OF 28R, WHEN I REALIZED ^PRIVACY DATA OMITTED^ WAS AN EMERGENCY.  ATC NOTICED IT WAS APPARENT THAT ^PRIVACY DATA OMITTED^ WAS TURNING TOWARDS RUNWAY 28R.  ATC CLEARED ^PRIVACY DATA OMITTED^ TO LAND ON 28L TO KEEP RUNWAY SEPARATION WITH THE INBOUND AIRCRAFT.  WHEN IT WAS APPARENT THAT ^PRIVACY DATA OMITTED^ WAS ATTEMPTING TO SET IT DOWN ON 28R.  ^PRIVACY DATA OMITTED^ LANDED LEFT OF 28R.  EMERGENCY VEHICLES WERE CALLED TO 28R AND THE RUNWAY WAS CLOSED.

AS OF NOW I CONSIDER THIS INCIDENT CLOSED.   IF MORE INFORMAITON IS PRESENTED, THE REPORT WILL BE AMENDED.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.