Aero Sp Z O O AT-4 LSA accident near Delaware, Ohio, July 28, 2010
On July 28, 2010 at about 5:40 pm local time, a Aero Sp Z O O AT-4 LSA, registered N8549S, was substantially damaged in an accident during approach (VFR pattern base) near Delaware, Ohio (Delaware Municipal Airport). It was a personal flight under general aviation rules (Part 91). 1 person was killed. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot’s failure to maintain adequate airspeed which resulted in a stall and subsequent loss of control of the airplane.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- July 28, 2010 · about 5:40 pm local time · cases in 2010
- Place
- Delaware, Ohio · Delaware Municipal Airport · cases near this airport · map
- Type
- Accident
- Injuries
- 1 person was killed.
- Weather
- visual conditions (good weather)
- Aircraft
- Aero Sp Z O O AT-4 LSA · all AT-4 LSAs on the register
- Registration
- N8549S · no longer on the register · serial AT4-004
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
Several witnesses, who were close to the airport, reported seeing the airplane enter the traffic pattern for a landing. The witnesses stated that the airplane made steep turns, with the wings near vertical, at high angles of attack, while maneuvering in the traffic pattern. The witnesses also said it appeared the airplane then did a "backward roll," entered a spin, and descended to the ground. The airplane impacted trees and terrain near the approach end of the runway. A postaccident examination of the airplane wreckage revealed no preimpact anomalies that would have precluded normal operation.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Loss of control in flight during approach (VFR pattern base) defining event
- Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent
The NTSB's findings
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Airspeed › Not attained/maintained
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › (general) › Not attained/maintained
Pilot
- Certificate: private
- Ratings: single-engine land; instrument: airplane
- Flight time: 1,280 hours in all; 6 in this make and model
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: fatal
The aircraft
- Airframe total time: 644 hours
- Last inspection: 100-hour inspection, July 17, 2010; 2 hours since
- Maximum gross weight: 1,320 lb
- Seats: 2
- Landing gear: fixed
- Engine: Rotax 912ULS (piston); 0 hours total
- Fire on the ground
The flight
- Departed from: DLZ Delaware OH at 5:00 pm
- Destination: DLZ Delaware OH
- Flight plan: not recorded
- Runway 28, 5,000 ft by 100 ft
Weather at the time
- Light: daylight
- Wind: from 230° at 9 knots
- Visibility: 10 statute miles
- Sky: broken clouds at 3,600 ft; scat at 2,800 ft
- Temperature: 86°F (30°C), dew point 73°F (23°C)
- Altimeter: 30.04 inHg
- Observation at 4:53 pm from OSU, 12 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
11 documents, released by the NTSB on September 30, 2011. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Photo 1 (Provided by FAA) | PDF, 1 page | View Download |
| 2 | Photo 2 (Provided by FAA) | PDF, 1 page | View Download |
| 3 | Photo 3 (Provided by FAA) | PDF, 1 page | View Download |
| 4 | Photo 4 (Provided by FAA) | PDF, 1 page | View Download |
| 5 | Photo 5 (Provided by FAA) | PDF, 1 page | View Download |
| 6 | Photo 6 (Provided by FAA) | PDF, 1 page | View Download |
| 7 | Photo 7 (Provided by FAA) | PDF, 1 page | View Download |
| 8 | Witness Statements | PDF, 5 pages | View Download |
| 9 | Toxicological Report | PDF, 2 pages | View Download |
| 10 | Photo 8 (Provided by FAA) | PDF, 1 page | View Download |
| 11 | Maintenance Records | PDF, 5 pages | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Other NTSB records under N8549S the same tail number, which may have belonged to a different aircraft at the time
Connections how this case links to the rest of the register
- N8549S: not on the register today · the record of its deregistration
- Aero Sp Z O O AT-4 11 registered today · the model family and its accident history
- Aero Sp Z O O 11 aircraft on the register
- Engine: Rotax 912ULS 63 aircraft carry this series today · as the NTSB recorded it
- Delaware Muni/Jim Moore Field · nearest airport
- Accidents and incidents in Ohio 1,884 since 1982 · 253 in the last ten years
- Ohio 8,531 aircraft registered
- Other NTSB records under N8549S 1 records · the number may have belonged to another aircraft at the time
The whole map of how records connect · these connections as data: /graph/accident/CEN10LA470.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
