N247EA squawked 7700 near Glendale, United States
What the ADS-B data shows about this general emergency event, and what it does not.
Safe Skies › 18 Nov 2026 › N247EA
NO LONGER SQUAWKING Last updated 18 Nov 2026, 15:28 UTC
N247EA (PIAT) transmitted squawk 7700 for 6 minutes from 15:22 UTC on 18 Nov 2026. Last seen 8 km from Luke Air Force Base.
Squawk 7700 means general emergency. Pilots squawk 7700 to tell air traffic control they have an emergency and need priority. The code alone does not say what the problem is.
The aircraft
| Callsign | N247EA |
|---|---|
| Registration | N247EA |
| Type | PIAT (PIAT) |
| Operator or owner (database field) | MESA PILOT DEVELOPMENT LLC |
| Registered in | United States |
| ICAO 24-bit address | A24A65 |
Track while squawking 7700
Coloured line, open circle to filled circle: the aircraft while it transmitted 7700. Black squares: nearby airports. Positions come from volunteer ADS-B receivers and can have gaps.
Altitude
Timeline
- 15:39 UTC · Update: 10 min after the squawk was last observed; Last observed on the ground near Luke Air Force Base (8 km).
- 15:28 UTC · Page created: the observation met the publication rules
- 15:22 UTC · Squawk 7700 first observed
What we know, and what we don’t
Known from the data: the aircraft transmitted 7700 for about 6 minutes, the positions and altitudes above, and where it was last seen with the code.
Outcome as far as the squawk data shows: Last observed on the ground near Luke Air Force Base (8 km). When an aircraft stops squawking the code, the crew may have cancelled it, switched transponders, or landed; we only know it is no longer observed.
Not known: why the crew chose this code, whether anything was actually wrong, and what happened next unless an official source or reputable report says so below. We do not guess.
What squawk 7700 usually involves
- Fuel problems, a medical emergency on board, an engine or systems fault, smoke or fire warnings, a pressurisation problem, or any other situation where the crew wants priority handling.
- Controllers see the code flash on their screens, clear traffic out of the way, and offer the nearest suitable runway. Fire and rescue services are often put on standby; that is a precaution, not a sign that something has gone wrong.
- Most 7700 events end with an ordinary landing. Many are precautionary, and a good number are cleared within minutes.
- The code does not say what the problem is. Crews declare an emergency for a reason they judge sufficient; that reason is rarely public in real time.
- Occasionally the code is selected by mistake or while testing equipment, which is why short events are common.
Weather near the last position
Latest report near the time, at Phoenix Sky Harbor International Airport (KPHX, 29 km away):
METAR KPHX 181451Z 21003KT 10SM FEW250 12/08 A3012 RMK AO2 SLP191 T01170083 53010
Source: aviationweather.gov. This is the nearest station’s report, not necessarily the conditions the aircraft flew in.
Everything that squawked on 18 Nov 2026 · How common is this? · Methodology
Safe Skies by pereJets. Data: ADS-B position reports from The OpenSky Network (opensky-network.org), combined with public aircraft databases. Published automatically by rule; see the methodology. Event e6afdc2d3a24a65.
Embed this on your site
Free to embed. The widget links back to the source.
<iframe src="https://perejets.com/flight-facts/embed/n247ea-squawk-7700-2026-11-18/" width="100%" height="300" style="border:1px solid #d7dde2;border-radius:10px;max-width:640px" title="Safe Skies by pereJets" loading="lazy"></iframe>
Spot an error, or know more?
Tell us what is wrong or what you know. We correct pages quickly and note the correction on the page. If you are the owner or operator and want a page reviewed, choose “Privacy or removal request”: the page is taken out of search results straight away while we look at it.