- Date
- April 27, 1972
- Place
- Council Grve, KS · COUNCIL GRVE, KS
- Injuries
- 1 fatal, 1 serious
- Damage
- Destroyed
- Phase of flight
- Enroute
- Aircraft
- N1269BLuscombe 8A
- Status
- Completed · report February 15, 1973
- Report
- Brief approved by the director
- Case key
- 166077
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-1942 72/4/27 COUNCIL GRVE,KANS LUSCOMBE 8A CR- 0 1 0 NONCOMMERCIAL PRIVATE, AGE 46, 408 TIME - 1250 N1269B PX- 1 0 0 PLEASURE/PERSONAL TRANSP TOTAL HOURS, UNK/NR IN DAMAGE-DESTROYED OT- 0 0 0 TYPE, NOT INSTRUMENT RATED. DEPARTURE POINT INTENDED DESTINATION LIBERAL,KANS GRIFFITH,IND TYPE OF ACCIDENT PHASE OF OPERATION COLLIDED WITH: ELECTRONIC TOWERS IN FLIGHT: OTHER PROBABLE CAUSE(S) PILOT IN COMMAND - CONTINUED VFR FLIGHT INTO ADVERSE WEATHER CONDITIONS PILOT IN COMMAND - FAILED TO SEE AND AVOID OBJECTS OR OBSTRUCTIONS WEATHER - LOW CEILING FACTOR(S) WEATHER - RAIN WEATHER - FOG TERRAIN - HIGH OBSTRUCTIONS WEATHER BRIEFING - BRIEFED BY FLIGHT SERVICE PERSONNEL, BY PHONE WEATHER FORECAST - FORECAST SUBSTANTIALLY CORRECT SKY CONDITION CEILING AT ACCIDENT SITE OVERCAST 500 VISIBILITY AT ACCIDENT SITE PRECIPITATION AT ACCIDENT SITE 1 MILE OR LESS DRIZZLE, RAIN OBSTRUCTIONS TO VISION AT ACCIDENT SITE WIND VELOCITY-KNOTS FOG CALM TYPE OF WEATHER CONDITIONS TYPE OF FLIGHT PLAN VFR NONE REMARKS- HIT 500FT TV RELAY TOWER CABLE.
Aircraft
- Registration
- N1269B
- Reported as
- Luscombe 8A
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Destroyed
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.