WPR14CA279 · Wiley Kitfox IV
Wiley Kitfox IV · Accident: collision during takeoff/landing on approach
From Sprague, WA to Sprague, WA
Event
- NTSB case
- WPR14CA279
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Wiley Kitfox IV
- Aircraft type
- Wiley KITFOX
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N5KW
- Operator
- Walker Mark L
- Onboard fatalities
- Unknown
- Route
- From Sprague, WATo Sprague, WA
- Aircraft age
- About 20 years (built 1994)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Approach
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Collision during takeoff/landing
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Wire
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Environmental issues › Physical environment
- Personnel issues › Psychological
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot stated that the purpose of the flight was to practice taxiing in his recently purchased airplane. While taxiing, the airplane unintentionally became airborne and the pilot decided that in an effort to not collide with an electric fence ahead, he would need to add full power and fly the airplane in a traffic pattern to come back and land. Despite being aware of a powerline in the area, the pilot collided with it during his third landing attempt. The pilot reported no preimpact mechanical malfunctions or failures that would have precluded normal operation.
Probable cause
The pilot's failure to maintain adequate clearance from powerlines during the landing approach resulting in a collision.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR14CA279
- Event ID
- 20140703X44945
- Case number
- WPR14CA279
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2014-07-03.
- API snapshot SHA-256: adc02b1187e67da2dfe19d17b964c8a9322c4eeeeba7379bf272c974cee5588b; retrieved 2026-09-16T00:48:41.866Z.