Go-around — N628CB
KBDN · 162026-07-24 00:30 UTC· KPDT → KBDN· CIMARRON AVIATION INC· C25B
N628CB (Cimarron Aviation) was operating from KPDT to KBDN on 2026-07-24. SkyMeter detected a go-around at Bend Municipal Airport (KBDN) on runway 16 at 00:30 UTC. Trace data at the event: 4253 ft AGL, 185 kt GS. METAR at the time reported 7 kt wind, 5 kt crosswind component, 16,093 m visibility. A go-around is a discontinued landing approach in which the pilot adds power and climbs back to a safe altitude before re-attempting the approach or proceeding to an alternate. It is a routine safety response, not an emergency, and is taught as the standard reaction to any unstable approach. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- HAZARDS6/6151 2026-07-16 15:28Z – 2026-07-30 04:00Z SFC–8,000 ft
18NM W SPRAY, OR, Thursday, July 16, 2026 through Thursday, July 30, 2026 UTC
View FAA NOTAM → - HAZARDS6/6458 2026-07-17 15:40Z – 2026-08-01 04:00Z SFC–9,000 ft
9NM E MADRAS, OR, Friday, July 17, 2026 through Saturday, August 1, 2026 UTC
View FAA NOTAM → - HAZARDS6/6572 2026-07-18 03:14Z – 2026-07-31 04:00Z SFC–11,000 ft
18NM SE PRINEVILLE, OR, Saturday, July 18, 2026 through Friday, July 31, 2026 UTC
View FAA NOTAM → - HAZARDS6/6695 2026-07-18 20:09Z – 2026-07-31 04:00Z SFC–9,000 ft
12NM SE MADRAS, OR, Saturday, July 18, 2026 through Friday, July 31, 2026 UTC
View FAA NOTAM → - HAZARDS6/6734 2026-07-19 01:25Z – 2026-08-01 04:00Z SFC–9,000 ft
26NM E MADRAS, OR, Sunday, July 19, 2026 through Saturday, August 1, 2026 UTC
View FAA NOTAM → - HAZARDS6/6756 2026-07-19 15:45Z – 2026-08-02 04:00Z SFC–8,000 ft
39NM NW JOHN DAY, OR, Sunday, July 19, 2026 through Sunday, August 2, 2026 UTC
View FAA NOTAM → - HAZARDS6/6757 2026-07-19 16:07Z – 2026-08-02 04:00Z SFC–9,000 ft
12NM SE MADRAS, OR, Sunday, July 19, 2026 through Sunday, August 2, 2026 UTC
View FAA NOTAM → - HAZARDS6/6778 2026-07-19 19:09Z – 2026-08-03 03:00Z SFC–8,000 ft
1NM S FOSSIL, OR, Sunday, July 19, 2026 through Monday, August 3, 2026 UTC
View FAA NOTAM → - HAZARDS6/6812 2026-07-19 23:08Z – 2026-08-03 03:00Z SFC–11,000 ft
23NM SE PRINEVILLE, OR, Sunday, July 19, 2026 through Monday, August 3, 2026 UTC
View FAA NOTAM → - HAZARDS6/6855 2026-07-20 01:34Z – 2026-08-03 03:00Z SFC–11,000 ft
45NM NW BURNS, OR, Monday, July 20, 2026 through Monday, August 3, 2026 UTC
View FAA NOTAM → - HAZARDS6/7177 2026-07-20 22:03Z – 2026-08-04 04:00Z SFC–8,000 ft
1NM W CONDON, OR, Monday, July 20, 2026 through Tuesday, August 4, 2026 UTC
View FAA NOTAM → - HAZARDS6/7611 2026-07-22 03:41Z – 2026-08-05 04:00Z SFC–8,000 ft
1NM S FOSSIL, OR, Wednesday, July 22, 2026 through Wednesday, August 5, 2026 UTC
View FAA NOTAM → - HAZARDS6/7612 2026-07-22 03:47Z – 2026-08-04 04:00Z SFC–9,000 ft
26NM E MADRAS, OR, Wednesday, July 22, 2026 through Tuesday, August 4, 2026 UTC
View FAA NOTAM → - HAZARDS6/8112 2026-07-23 17:45Z – 2026-08-06 04:00Z SFC–11,000 ft
45NM NW BURNS, OR, Thursday, July 23, 2026 through Thursday, August 6, 2026 UTC
View FAA NOTAM → - HAZARDS6/8322 2026-07-23 22:15Z – 2026-07-30 05:00Z SFC–8,000 ft
8NM NE MADRAS, OR, Thursday, July 23, 2026 through Thursday, July 30, 2026 UTC
View FAA NOTAM →
SkyMeter cross-referenced this flight against FAA-published TFRs that were active during its window and within its geographic bounding box. Overlap doesn't necessarily mean violation — the aircraft may have been outside the TFR’s precise polygon or flying under air-traffic-control coordination.
Pilot review data
- Runway 16
- 4253 ft AGL at event
- 185 kt ground speed
- 0 fpm vertical
- 7 kt wind
- 5 kt crosswind component
- 16,093 m visibility
- METAR KBDN 160655Z AUTO 30005KT 10SM -RA BKN060 OVC070 11/08 A3004 RMK AO2 P0002
Flight context
- N628CB
- Cimarron Aviation
- C25B
- KPDT → KBDN
- 2026-07-24 00:30 UTC
- KBDN runway 16
Automated analysis. Events shown on this page (such as go-around, unstable approach, or runway events) are heuristic classifications produced by algorithms from publicly broadcast ADS-B data. They are intended to surface flights of interest for further review — they are not findings of fact, and they do not determine pilot fault, regulatory compliance, or the cause of any occurrence. Coverage gaps and sensor noise can affect accuracy. Only the relevant civil aviation authority or accident investigation body can make official determinations. How we detect events · Dispute or correct this data