N278AZ

278AZ LLC · SJT → KGKY

N278AZ is operated by 278AZ LLC between San Angelo Regional Mathis Field (KSJT) and Arlington Municipal Airport (KGKY). The flight is most often flown by a CIRRUS Cirrus SR-22 Turbo. Typical block time is 1h 51m. SkyMeter has observed 72 legs of this flight number via ADS-B.

✈
FLIGHTS
72
last 90 days
⏱
AVG DURATION
1h 51m
tracked time
📅
SERVICE PERIOD
5/27/2025 → 8/15/2026
first → last seen
🗺
ROUTES / TYPES
49 / 1
city pairs · airframes
⚠
INCIDENT RATE
8.3%
6 flagged

Routes flown

By count · last 90 days

10
KSJT → KGKY
3
avg 1h 14m · San Angelo Regional Mathis Field → Arlington
KSJT → KBAZ
2
avg 1h 4m · San Angelo Regional Mathis Field → New Braunfels
KAUS → KSJT
2
avg 1h 20m · Austin Bergstrom → San Angelo Regional Mathis Field
KSJT → KAUS
2
avg 1h 10m · San Angelo Regional Mathis Field → Austin Bergstrom
KE30 → KSJT
2
avg 8m · Bruce Field → San Angelo Regional Mathis Field
KGTU → KABI
1
avg 20h 59m · Georgetown → Abilene
KSJT → KT67
1
avg 1h 10m · San Angelo Regional Mathis Field → Hicks Air Field
KDAL → KSJT
1
avg 1h 16m · Dallas Love Field → San Angelo Regional Mathis Field
KIWS → KSJT
1
avg 1h 33m · West Houston → San Angelo Regional Mathis Field
KSJT → KJWY
1
avg 1h 12m · San Angelo Regional Mathis Field → Mid-Way

Aircraft types

Equipment used on this number

1
S22T CIRRUS Cirrus SR-22 Turbo
74

Safety profile

Flagged flights · last 90 days

Go-arounds
0
Unstable approach
6
Rejected TO
0
Stall warnings
0
Overspeeds
0
Runway excursion
0
Counts represent flights with at least one occurrence of each flag, not the total event count. See /incidents for individual events.

Recent flights

Newest 30 operations of N278AZ

30
N278AZCIRRUS Cirrus SR-22 Turbo
→
8/15/2026
1h 13m
No alerts
Replay Analysis
N278AZCIRRUS Cirrus SR-22 Turbo
→
8/12/2026
3h 6m
No alerts
Replay Analysis
N278AZCIRRUS Cirrus SR-22 Turbo
→
8/11/2026
2h 56m
No alerts
Replay Analysis
N278AZCIRRUS Cirrus SR-22 Turbo
→
8/11/2026
1h 10m
No alerts
Replay Analysis
N278AZCIRRUS Cirrus SR-22 Turbo
→
8/11/2026
29m
No alerts
Replay Analysis
N278AZCIRRUS Cirrus SR-22 Turbo
→
8/11/2026
1h 9m
No alerts
Replay Analysis
N278AZCIRRUS Cirrus SR-22 Turbo
→
8/11/2026
1h 10m
△ Low approach-stability score
Replay Analysis
N278AZCIRRUS Cirrus SR-22 Turbo
→
8/9/2026
47m
No alerts
Replay Analysis
N278AZCIRRUS Cirrus SR-22 Turbo
→
8/8/2026
1h 14m
△ Low approach-stability score
Replay Analysis
N278AZCIRRUS Cirrus SR-22 Turbo
→
8/8/2026
8m
No alerts
Replay Analysis
N278AZCIRRUS Cirrus SR-22 Turbo
→
8/7/2026
58m
No alerts
Replay Analysis
N278AZCIRRUS Cirrus SR-22 Turbo
→
8/7/2026
1h 12m
△ Low approach-stability score
Replay Analysis
N278AZCIRRUS Cirrus SR-22 Turbo
→
8/6/2026
1h 5m
No alerts
Replay Analysis
N278AZCIRRUS Cirrus SR-22 Turbo
→
8/3/2026
1h 10m
No alerts
Replay Analysis
N278AZCIRRUS Cirrus SR-22 Turbo
→
8/2/2026
1h 17m
No alerts
Replay Analysis
N278AZCIRRUS Cirrus SR-22 Turbo
→
8/2/2026
1h 12m
No alerts
Replay Analysis
N278AZCIRRUS Cirrus SR-22 Turbo
→
8/1/2026
1h 15m
No alerts
Replay Analysis
N278AZCIRRUS Cirrus SR-22 Turbo
→
7/31/2026
1h 24m
No alerts
Replay Analysis
N278AZCIRRUS Cirrus SR-22 Turbo
→
7/28/2026
1h 5m
△ Low approach-stability score
Replay Analysis
N278AZCIRRUS Cirrus SR-22 Turbo
→
7/28/2026
1h 6m
No alerts
Replay Analysis
N278AZCIRRUS Cirrus SR-22 Turbo
→
7/27/2026
7m
No alerts
Replay Analysis
N278AZCIRRUS Cirrus SR-22 Turbo
→
7/26/2026
1h 13m
No alerts
Replay Analysis
N278AZCIRRUS Cirrus SR-22 Turbo
→
7/26/2026
1h 15m
△ Low approach-stability score
Replay Analysis
N278AZCIRRUS Cirrus SR-22 Turbo
→
7/23/2026
1h 32m
No alerts
Replay Analysis
N278AZCIRRUS Cirrus SR-22 Turbo
→
7/23/2026
1h 43m
No alerts
Replay Analysis
N278AZCIRRUS Cirrus SR-22 Turbo
→
7/22/2026
43m
No alerts
Replay Analysis
N278AZCIRRUS Cirrus SR-22 Turbo
→
7/22/2026
51m
No alerts
Replay Analysis
N278AZCIRRUS Cirrus SR-22 Turbo
→
7/17/2026
1h 24m
No alerts
Replay Analysis
N278AZCIRRUS Cirrus SR-22 Turbo
→
7/17/2026
1h 8m
No alerts
Replay Analysis
N278AZCIRRUS Cirrus SR-22 Turbo
→
7/12/2026
45m
No alerts
Replay Analysis
© SkyMeter · All flight data subject to ODbL attribution · Tracked: 90-day window