The U.S. aircraft register, updated daily · Carbon Free Flight by 2050
Accidents · NTSB ERA12CA167 · Final report

Remos Aircraft GMBH G-3/600 accident near Sarasota, Florida, January 29, 2012

On January 29, 2012 at about 7:24 pm local time, a Remos Aircraft GMBH G-3/600, registered N133LS, was substantially damaged in an accident during landing (landing roll) near Sarasota, Florida (Sarasota/Bradenton Intl airport). It was an instructional 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).

Preview. This page is not yet listed for search engines.

The NTSB's probable cause their words, unchanged

The student pilot’s loss of directional control during the landing roll.

Source: NTSB aviation accident database, copy made October 4, 2026. Docket and reports at the NTSB.

What the record shows

Date
January 29, 2012 · about 7:24 pm local time
Place
Sarasota, Florida · Sarasota/Bradenton Intl · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Remos Aircraft GMBH G-3/600 · all G-3/600s on the register
Registration
N133LS · registry record · serial 217
Damage
Substantial damage
Flight
Instructional flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The student pilot was conducting solo touch-and-go landings. He stated that, during the fifth landing, just after touchdown, the airplane veered left. The pilot applied right rudder, but the airplane continued left and exited the left side of the runway. The airplane's nose landing gear collapsed, resulting in substantial damage to the firewall. The pilot reported that there were no preaccident mechanical malfunctions or failures 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

  1. Loss of control on ground during landing (landing roll) defining event
  2. Runway excursion during landing (landing roll)

The NTSB's findings

  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Directional control › Not attained/maintained
  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Student pilot

Pilot

  • Certificate: student
  • Flight time: 46 hours in all; 46 in this make and model
  • Medical certificate: Class 3 (without waivers/limitations)
  • Seat: left

The aircraft

  • Airframe total time: 5,636 hours
  • Last inspection: annual inspection, October 26, 2011
  • Maximum gross weight: 1,320 lb
  • Seats: 2
  • Landing gear: fixed
  • Engine: Rotax 912ULS (piston); 0 hours total
  • Operator: Oars Ply The Sky LLC

The flight

  • Departed from: SRQ Sarasota FL
  • Destination: SRQ Sarasota FL
  • Flight plan: none
  • Runway 04, 5,009 ft by 150 ft

Weather at the time

  • Light: daylight
  • Wind: from 020° at 8 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 75°F (24°C), dew point 43°F (6°C)
  • Altimeter: 30.20 inHg
  • Observation at 7:53 pm from SRQ

Injuries

FatalSeriousMinorNone
Flig1

Other NTSB records under N133LS the same tail number, which may have belonged to a different aircraft at the time

2023-06-01CEN23LA216 · accident near Sugar Grove, IL · substantial damage · no injuries

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 docket at the NTSB holds the report as a PDF and the investigation's photographs and documents. This site 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 ERA12CA167.