- Date
- December 9, 1967
- Place
- Detroit, MI · DETROIT, MI
- Injuries
- 2 minor
- Damage
- Destroyed
- Phase of flight
- Landing
- Aircraft
- N822LJLear Jet 23
- Status
- Completed · report August 19, 1968
- Report
- Brief approved by the director
- Case key
- 112502
From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.
On this page
NTSB brief
NTSB’s brief of the accident, as it was printed: the coded facts, with the probable cause and factors.
---------------------------------------------------------------------------------------------------------------------------- FILE DATE LOCATION AIRCRAFT DATA INJURIES FLIGHT PILOT DATA F S M/N PURPOSE ---------------------------------------------------------------------------------------------------------------------------- 3-4792 67/12/9 DETROIT,MICH LEAR JET 23 CR- 0 0 2 COMMERCIAL AIRLINE TRANSPORT, AGE TIME - 1257 N822LJ PX- 0 0 0 AIR TAXI-CARGO 31, 3500 TOTAL HOURS, 815 DAMAGE-DESTROYED OT- 0 0 0 IN TYPE, INSTRUMENT RATED. NAME OF AIRPORT - DETROIT CITY TYPE OF ACCIDENT PHASE OF OPERATION HARD LANDING LANDING: LEVEL OFF/TOUCHDOWN NOSE OVER/DOWN LANDING: ROLL PROBABLE CAUSE(S) PILOT IN COMMAND - IMPROPER LEVEL OFF PILOT IN COMMAND - SELECTED WRONG RUNWAY RELATIVE TO EXISTING WIND FACTOR(S) WEATHER - UNFAVORABLE WIND CONDITIONS WEATHER BRIEFING - BRIEFED BY WEATHER BUREAU PERSONEL, BY PHONE WEATHER FORECAST - UNKNOWN/NOT REPORTED SKY CONDITION CEILING AT ACCIDENT SITE UNKNOWN/NOT REPORTED 1300 VISIBILITY AT ACCIDENT SITE PRECIPITATION AT ACCIDENT SITE 4 MILES OR LESS NONE OBSTRUCTIONS TO VISION AT ACCIDENT SITE RELATIVE BEARING OF WIND SMOKE RIGHT CROSS WIND 068-112 DEGREES WIND DIRECTION-DEGREES WIND VELOCITY-KNOTS 50 10 TYPE OF WEATHER CONDITIONS TYPE OF FLIGHT PLAN VFR IFR REMARKS- RT CROSS WIND 80 DEG 10 KNOTS GUSTING 18 KNOTS.
Aircraft
- Registration
- N822LJ
- Reported as
- Lear Jet 23
- Category
- Airplane
- Engine
- turbo jet
- Damage
- Destroyed
- Airport
- Detroit City
Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.