# Incident 20260204001659I: Mk30 MK30, Richardson, TX, February 4, 2026

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: February 4, 2026, 16:04 local time
- Place: Richardson, TX
- Damage: Destroyed
- Phase of flight: Climb
- Operating rules: Air taxi and commuter (Part 135)
- Operator: 4MZA
- Location: 32.9723° N, 96.7081° W: Placed by OpenAirDocs: center of Richardson, TX, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=32.9723&lon=-96.7081&mi=10
- Aircraft: N642PA, registered now (https://openairdocs.org/aircraft/N642PA) (OpenAirDocs)
- Registry model: Amazon.Com Services MK30 (registry code 06102FK, https://openairdocs.org/model/amazon-com-services-mk30) (OpenAirDocs)
- Reported make and model: MK30 MK30
- People aboard: 0
- Fatal injuries: 0
- Other injuries: 0
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20260204001659I

## Narrative

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

ON FEBRUARY 4, 2026, THE MK30 WAS CONDUCTING A COMMERCIAL FLIGHT AT A COMMERCIAL FACILITY IN RICHARDSON, TX. THE DRONE TOOK OFF AND DELIVERED THE PACKAGE. JUST AFTER DELIVERY, ASCENT FROM THE DELIVERY POINT, THE DRONE CONTACTED THE MULTI-UNIT BUILDING THAT WAS THE DELIVERY SITE. TELEMETRY AND LOG FOOTAGE CONFIRMED THAT DURING ASCENT, THE DRONE CAME INTO CONTACT WITH THE BUILDING AT APPROXIMATELY 65’. THE DRONE EXPERIENCED SIGNIFICANT DAMAGE AND IMPACTED THE GROUND.

THE DRONE SUSTAINED SIGNIFICANT DAMAGE, INCLUDING ADDITIONAL DAMAGE UPON IMPACT WITH THE GROUND. THERE WERE NO INJURIES. THERE WAS SURFACE DAMAGE TO THE MULTI-UNIT BUILDING, BUT NO SIGNIFICANT DAMAGE TO THIRD PARTY PROPERTY. THE FIRE DEPARTMENT WAS CALLED BUT LEFT SHORTLY AFTER ARRIVING AFTER DETERMINING THERE WAS NO RISK.

POST-FLIGHT LOGS CONFIRMED THAT DURING THE CLIMB, MULTIPLE GLOBAL POSITIONING SATELLITES BEGAN EXHIBITING POSITION ESTIMATION ERRORS THAT INTENSIFIED WITH ALTITUDE. THE SIGNALS FROM MULTIPLE SATELLITES WERE NOT CONSISTENT ACROSS THE SET OF SATELLITES.  THE GPS SATELLITE CONSTELLATION SYSTEM APPEARED TO BE FUNCTIONAL. DISTORTED GPS SIGNALS WERE A RESULT OF THE ENVIRONMENT AROUND THE MULTI-UNIT BUILDING (STRUCTURAL INFERENCE).  DESPITE HAVING FAULT DETECTION AND FAULT EXCLUSION CAPABILITY FROM THE GPS RECEIVERS, THE PARAMETERS FOR THE GPS SATELLITE ERROR VIA STRUCTURAL INTERFERENCE WERE BELOW THE GPS RECEIVER FILTER TOLERANCE FOR FAULT DETECTION / EXCLUSION CAPABILITY.  AS A RESULT, THE AIRCRAFT COULD NOT ACCURATELY DETERMINE ITS POSITION RELATIVE TO ITS EXACT LOCATION POST-DELIVERY.

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.