Aero Sp Z O O AT-4 LSA accident near Colorado Springs, Colorado, July 26, 2011
On July 26, 2011 at about 1:30 pm local time, a Aero Sp Z O O AT-4 LSA, registered N1277K, was substantially damaged in an accident during landing (flare/touchdown) near Colorado Springs, Colorado (Meadow Lake airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot's failure to maintain proper approach speed and his inadequate recovery from a bounced landing.
Source: NTSB aviation accident database, copy made October 4, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- July 26, 2011 · about 1:30 pm local time
- Place
- Colorado Springs, Colorado · Meadow Lake · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Aero Sp Z O O AT-4 LSA · all AT-4 LSAs on the register
- Registration
- N1277K · registry record · serial AT4-015
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The student pilot was attempting to land when the airplane's descent rate increased, resulting in a hard landing and a bounce. The airplane nosed over prior to the touchdown, allowing the propeller to strike the runway and causing the nose landing gear to buckle and collapse before the airplane skidded to a stop. The airplane sustained substantial damage to the firewall. A postaccident examination did not reveal any anomalies with the airplane that would have prevented 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
- Abnormal runway contact during landing (flare/touchdown) defining event
The NTSB's findings
- cause Personnel issues › Action/decision › Action › Incorrect action performance › Student pilot
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › (general) › Not attained/maintained
Dual student
- Certificate: student
- Flight time: 50 hours in all; 15 in this make and model
- Medical certificate: Class 3
- Seat: left
- Injury: no injuries
The aircraft
- Last inspection: inspection type not recorded
- Seats: 2
- Landing gear: fixed
- Engine: Rotax 912ULS (piston); 0 hours total
- Operator: Skyraider Aviation INC
The flight
- Departed from: KEIK Erie CO
- Destination: KEIK Erie CO
- Flight plan: none
- Runway 33, 6,000 ft by 60 ft
Weather at the time
- Light: daylight
- Wind: from 300° at 3 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 68°F (20°C), dew point 55°F (13°C)
- Altimeter: 30.10 inHg
- Observation at 1:32 pm from KFLY
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.
About this page
Everything above comes from the NTSB's public accident database: the narrative, probable cause and findings are the NTSB's own words, and the coded tables behind its report (pilot, aircraft, flight, weather, injuries, sequence of events) are written out in plain English. Pilots' ages, home towns and medical details are left out on purpose. The documents and photographs are the NTSB's docket, the folder of records gathered during the investigation, shown as the NTSB released them (the NTSB redacts some personal details first) and listed under the NTSB's own titles. This site's own text never names pilots, passengers or anyone else involved. A preliminary report describes what is known soon after the event and can change; the final report, with the probable cause, usually follows one to two years later and this page is refreshed when it does. Case number CEN11CA519.