FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN09FA111 · Lantzair Flyers Inc LANCAIR 360

1 Jan 2009 · Joliet, IL, United States

Lantzair Flyers Inc LANCAIR 360 · Accident: loss of control in flight during takeoff

From Joliet Regional Airport (JOT) to Watertown Municipal Airport (RYV)

Report a problem

Event

NTSB case
CEN09FA111
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
2 · 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

Lantzair Flyers Inc LANCAIR 360

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
N3603R
Onboard fatalities
Unknown
Route
From Joliet Regional Airport (JOT), Joliet, ILTo Watertown Municipal Airport (RYV), Watertown, WI
Aircraft age
Not recorded
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
Takeoff
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
Loss of control in flight
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.

NTSB narrative

The pilot landed with 4 to 5 gallons of fuel on board following a 4.5-hour cross-country flight. After landing, the pilot made numerous attempts to locate fuel in order to continue the flight so that his passenger could be at work in the morning. The pilot left a note and money after having siphoned fuel from another airplane parked at the airport. After about 2 hours and 45 minutes on the ground, the airplane took off again. Impact marks indicate that the airplane stalled during the takeoff, impacting the terrain with the left wing prior to catching fire and coming to rest inverted. The accident occurred at night as the airplane was departing on the second leg of a cross-country flight. Calculations show that the airplane was slightly over the maximum gross takeoff weight and the center of gravity (CG) was slightly aft of the aft limit at the time of the accident. A pilot of another single-engine airplane, who landed a few minutes after the accident airplane landed, and who took off about 30 minutes later (which would have been about 2 hours before the accident) reported that he had to wipe a “slight frost buildup” off of his wings and tail with a towel prior to takeoff. The investigation could not determine whether the slight frost, slight overgross condition, or slight aft CG contributed, either individually or in combination, to the aerodynamic stall of the airplane. Additionally, several people reported that it was not uncommon to see deer on the airport property and one person reported seeing many deer on the runway earlier in the day prior to when the pilot landed; however the investigation could not determine whether deer were present on the runway at the time of the accident.

Probable cause

The pilot’s failure to maintain adequate flying speed during the night takeoff for undetermined reasons, which resulted in an inadvertent aerodynamic stall and subsequent loss of control

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN09FA111
Event ID
20090102X02015
Case number
CEN09FA111
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, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2009-01-02.
  • API snapshot SHA-256: f37dc6dcb548c86bec7bfbeb4bee6645d138773e7c38a8191416cd100e98de74; retrieved 2026-09-13T19:53:27.532Z.