FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MKC90LA047 · Burnett STARDUSTER TOO STARDUSTER

14 Jan 1990 · Lawrence, KS, United States

Burnett STARDUSTER TOO STARDUSTER · Accident: in flight collision with object on approach

From Lawrence Municipal Airport (LWC) to an unrecorded destination

Report a problem

Event

NTSB case
MKC90LA047
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
0
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

Burnett STARDUSTER TOO STARDUSTER

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
N4GB
Operator
Lburnett, Howard G. · private individual
Onboard fatalities
Unknown
Route
From Lawrence Municipal Airport (LWC), Lawrence, KSTo not recorded
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
Approach · VFR pattern final
First occurrenceThe 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
In flight collision with object
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Tree(s)
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

  • Pilot in command › Clearance, misjudged

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

THE COMMERCIAL PILOT SAID THAT WHILE ATTEMPTING TO LAND HIS HOMEBUILT BIPLANE ON HIS PRIVATE STRIP, HE WAS BLINDED BY THE SETTING SUN AND FAILED TO CLEAR A TREE ON FINAL APPROACH. THE ACFT'S RIGHT WING STRUCK THE TREE, WHICH CAUSED THE ACFT TO YAW TO THE RIGHT & CRASH. THE PLT SUFFERED A DAMAGED VERTEBRA, WHICH REQUIRED SURGERY.

Probable cause

THE PILOT MISJUDGED CLEARANCE FROM TREE(S) NEAR THE APPROACH END OF THE RUNWAY, WHILE ON FINAL APPROACH TO LAND. FACTORS RELATED TO THE ACCIDENT WERE: SUNGLARE, LACK OF VISUAL CUES TO THE PILOT, AND TREE(S).

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MKC90LA047
Event ID
20001212X22471
Case number
MKC90LA047
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: b2ea74ae9f600eb882ff4979f236d0fb57f9278385ca8d3fd927e504f56e755a; retrieved 2026-09-21T15:45:56.700Z.