- Date
- January 18, 1969
- Place
- Fairyland, GA · FAIRYLAND, GA
- Injuries
- 1 fatal
- Damage
- Destroyed
- Phase of flight
- Enroute
- Aircraft
- N459CMeyers 200
- Status
- Completed · report December 18, 1969
- Report
- Brief approved by the director
- Case key
- 191264
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-2611 69/1/18 FAIRYLAND,GA MEYERS 200 CR- 1 0 0 NONCOMMERCIAL PRIVATE, AGE 56, 1800 TIME - 1149 N459C PX- 0 0 0 PLEASURE/PERSONAL TRANSP TOTAL HOURS, 1200 IN DAMAGE-DESTROYED OT- 0 0 0 TYPE, NOT INSTRUMENT RATED. DEPARTURE POINT INTENDED DESTINATION LAST ENROUTE STOP HUNTSVILLE,ALA WINSTON-SALEM,NC FRANKLIN,NC TYPE OF ACCIDENT PHASE OF OPERATION COLLIDED WITH: TREES IN FLIGHT: OTHER PROBABLE CAUSE(S) PILOT IN COMMAND - ATTEMPTED OPERATION BEYOND EXPERIENCE/ABILITY LEVEL PILOT IN COMMAND - CONTINUED VFR FLIGHT INTO ADVERSE WEATHER CONDITIONS WEATHER - LOW CEILING WEATHER - RAIN WEATHER - FOG WEATHER BRIEFING - BRIEFED BY WEATHER BUREAU PERSONEL, BY PHONE WEATHER FORECAST - FORECAST SUBSTANTIALLY CORRECT SKY CONDITION CEILING AT ACCIDENT SITE OVERCAST 1300 VISIBILITY AT ACCIDENT SITE PRECIPITATION AT ACCIDENT SITE 2 MILES OR LESS RAIN OBSTRUCTIONS TO VISION AT ACCIDENT SITE WIND DIRECTION-DEGREES FOG 310 WIND VELOCITY-KNOTS TYPE OF WEATHER CONDITIONS 3 IFR TYPE OF FLIGHT PLAN NONE FIRE AFTER IMPACT REMARKS- MTN ENVELOPED IN CLDS.ACFT OBSVD IN DSNDG ATTITUDE APRX 30DEG.
Aircraft
- Registration
- N459C
- Reported as
- Meyers 200
- 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.