WPR13CA387 · TL Ultralight STINGSPORT
Arlington Flight Services TL Ultralight STINGSPORT · Accident: abnormal runway contact during landing
From Skagit Regional Airport (BVS) to Skagit Regional Airport (BVS)
Event
- NTSB case
- WPR13CA387
- 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
TL Ultralight STINGSPORT
- Aircraft type
- TL Ultralight STINGSPORT
- 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
- N9494
- Operator
- Arlington Flight Services
- Onboard fatalities
- Unknown
- Route
- From Skagit Regional Airport (BVS), Burlington, WATo Skagit Regional Airport (BVS), Burlington, WA
- Aircraft age
- About 6 years (built 2007)
- 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
- Landing · flare/touchdown
- 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
- Abnormal runway contact
- 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
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot rented the special light sport airplane from a fixed base operator for the purpose of conducting a personal flight to a non-towered airport, where he planned to practice landings and takeoffs. He entered a left traffic pattern for runway 11 at the destination airport, and conducted a normal touch-and-go landing and takeoff, with the intent of conducting at least one more touch-and-go on the same runway. He used the same flap and power settings for the second approach, but noted that the second approach was "slightly shallower than normal." After touchdown, the airplane bounced. The pilot maintained the pitch attitude, and the airplane touched down and bounced again. He then added power with the intent to abandon the landing, but the propeller struck the runway. The pilot reduced power and the airplane slid to a stop on the runway. The nose landing gear was collapsed aft, and penetrated the fuselage fuel tank, which resulted in substantial damage.
The pilot reported no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Probable cause
The pilot's improper flare and unsuccessful attempt to correct a bounced landing, which resulted in a nose gear collapse
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR13CA387
- Event ID
- 20130826X13248
- Case number
- WPR13CA387
- 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: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 45180f2b775fda9d6bc2988d4c0fd20cb3001d6d5d42c5c214ce135437fe5eaf; retrieved 2026-09-15T22:36:55.394Z.