Flying Cloud Airport: Runway Incursions
270 reported incursions · 1 serious (Category A/B) · Minneapolis, MN
By year
- 20268
- 202517
- 20248
- 202313
- 202211
- 202120
- 202010
- 201919
- 201818
- 201719
- 20168
- 201512
- 201410
- 20135
- 20124
- 20118
- 201015
- 200917
- 20087
- 20072
- 20062
- 20052
- 20043
- 20034
- 200228
By severity category
- Category D — no immediate safety consequence163
- Category C — ample margin to avoid a collision67
- Other / pre-2008 classifications39
- Category B — significant separation loss1
By type
- Pilot deviation174
- Vehicle or pedestrian55
- Air traffic control38
- Other / unknown3
Serious incursions (Category A and B)
2021-03-06 · Flying Cloud Airport · C172 / P28R · RWY 10L · Category B
AIRCRAFT 1 DID NOT CLEAR RUNWAY 10L AFTER BEING CLEARED TO CROSS THE RUNWAY. AIRCRAFT 1/C172 LANDED RUNWAY 10R AND EXITED THE RUNWAY AT TAXIWAY FOXTROT. LOCAL CONTROL INSTRUCTED AIRCRAFT 1 TO CROSS RWY 10L AND CONTACT GROUND. THE PILOT READ BACK WAS CORRECT. LC NOTICED AIRCRAFT 1 STOP IN THE MIDDLE OF RWY 10L. LC & GC ATTEMPTED SEVERAL TIMES TO CONTACT AIRCRAFT 1, BUT GOT NO REPLY. LC ISSUED GO-AROUND INSTRUCTIONS TO AIRCRAFT 2/P28R, ON SHORT FINAL TO RWY 10L, PRIOR TO RUNWAY THRESHOLD. AIRCRAFT 1 CHECKED ON WITH GC STATING THEY WERE CLEAR OF RWY 10R AT TWY F. GC ASKED AIRCRAFT 1 IF THEY WERE STOPPED ON RWY 10L, AIRCRAFT 1 REPLIED AFFIRMATIVE. AIRCRAFT 2 OVERFLEW AIRCRAFT 1 BY ESTIMATED 150'. GC INSTRUCTED AIRCRAFT 1 TO CONTINUE ACROSS THE RUNWAY WITHOUT DELAY
Counts are reported events, not a danger ranking. Before FY2008 the FAA used a narrower definition, so earlier years are not directly comparable.
Source: FAA Runway Safety (RWS) database, via ASIAS · United States Government public domain.