- Date
- February 15, 1968
- Place
- Plainville, CT · PLAINVILLE, CT
- Injuries
- 2 uninjured
- Damage
- Substantial damage
- Phase of flight
- Landing
- Aircraft
- N2751QCessna 182
- Status
- Completed · report May 7, 1968
- Report
- Brief approved by the director
- Case key
- 111449
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-0757 68/2/15 PLAINVILLE,CONN CESSNA 182 CR- 0 0 1 NONCOMMERCIAL COMMERCIAL, AGE 46, 1850 TIME - 1545 N2751Q PX- 0 0 1 CORP/EXEC TOTAL HOURS, 250 IN TYPE, DAMAGE-SUBSTANTIAL OT- 0 0 0 NOT INSTRUMENT RATED. NAME OF AIRPORT - ROBERTSON TYPE OF ACCIDENT PHASE OF OPERATION HARD LANDING LANDING: LEVEL OFF/TOUCHDOWN PROBABLE CAUSE(S) PILOT IN COMMAND - IMPROPER LEVEL OFF PILOT IN COMMAND - IMPROPER RECOVERY FROM BOUNCED LANDING FACTOR(S) WEATHER - UNFAVORABLE WIND CONDITIONS WEATHER BRIEFING - BRIEFED BY FLIGHT SERVICE PERSONNEL, BY PHONE WEATHER FORECAST - UNKNOWN/NOT REPORTED SKY CONDITION CEILING AT ACCIDENT SITE UNKNOWN/NOT REPORTED 4000 VISIBILITY AT ACCIDENT SITE PRECIPITATION AT ACCIDENT SITE 5 OR OVER(UNLIMITED) NONE OBSTRUCTIONS TO VISION AT ACCIDENT SITE RELATIVE BEARING OF WIND NONE LEFT QUARTERING HEAD WIND 293-337 DEGREES TEMPERATURE-F WIND DIRECTION-DEGREES 22 315 WIND VELOCITY-KNOTS TYPE OF WEATHER CONDITIONS 30 VFR TYPE OF FLIGHT PLAN NONE REMARKS- LT QUARTERING HEADWIND,30K WITH GUSTS.
Aircraft
- Registration
- N2751Q
- Reported as
- Cessna 182
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
- Airport
- Robertson
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.