NYC06FA071

NTSB accident investigation · Cessna 172R · Mitchellville, MD · February 22, 2006

Accident · FatalField investigationFinal report
Date
February 22, 2006, 09:50 local (14:50 UTC)
Place
Mitchellville, MD
Injuries
2 fatal, 1 serious
Damage
Destroyed
Phase of flight
Maneuvering
Aircraft
N3536CCessna 172R
Weather
Instrument (IMC) · Day
Status
Completed · report December 28, 2006
Report
Approved by Office Director
Parties
Cessna, Lycoming Engines, FAA
FAA report
20060222011889A
Case key
63264

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

Probable cause

The pilot's improper inflight planning/decision to attempt a landing in weather conditions below landing minimums, and his failure to maintain airspeed while maneuvering. Factors in the accident were the fog and snow.

Sequence of events

NTSB’s coding before 2008: each occurrence and phase of flight, and the causes and factors under it. The codes are defined in NTSB’s coding manual.

Abrupt maneuverManeuvering - turn to reverse direction
Flight into known adverse weather - continuedPilot in command
Weather condition - below approach/landing minimumsFactor
Acft/equip,inadequate compliance determinationPilot in command
Weather condition - fog
In-flight planning/decision - improperPilot in commandCause
Weather condition - snow
Loss of control - in flightManeuvering - turn to reverse direction
Airspeed - not maintainedPilot in commandCause
In flight collision with terrain/waterDescent - uncontrolled
Terrain condition - ground

Analysis

The airplane attempted two Global Positioning System instrument approaches to the destination airport in snow and fog, and descended 200 to 300 hundred feet below the minimum descent altitude of 700 feet each time. After the second approach, the airplane appeared out of the clouds over the south end of the runway, between 200 and 300 feet above the ground, and flew the length of the runway at low altitude. At the north end of the runway, the airplane turned west away from the airport, then circled to the right in a "dramatic" and "nose-high attitude" back towards the runway. The airplane overflew the runway headed south and turned west away from the airport, as engine power increased, and the flaps were retracted. The airplane then entered a steep left bank back towards the airport and "nose-dived" out of view. Seconds later, the sounds of impact were heard. Witnesses at the airport said the clouds were "on top of the trees" and that visibility was about 1/2 mile due to snow and fog. Examination of the wreckage revealed no mechanical deficiencies. Further examination of the airplane and its records revealed that the GPS database was expired, and that the airplane was above the manufacturer's maximum allowable gross weight.

Factual narrative

History of flight

On February 22, 2006, at 0950 eastern standard time, a Cessna 172R, N3536C, was destroyed during collision with terrain while maneuvering for landing after an instrument approach to Freeway Airport (W00), Mitchellville, Maryland. The certificated airline transport pilot and the private pilot were fatally injured, and the passenger was seriously injured. Instrument meteorological conditions prevailed for the flight that originated at Warrenton-Fauquier County Airport (W66), Warrenton, Virginia. An instrument flight rules (IFR) flight plan was filed for the personal flight conducted under 14 CFR Part 91.

The RNAV (GPS) Runway 36 approach at Freeway Airport had an inbound course of 345 degrees. The minimum descent altitude inside the final approach fix, which was BOKVE waypoint, was 700 feet. The BOKVE waypoint was 5 miles from the airport.

Radar data from the Federal Aviation Administration showed a target identified as the accident airplane approach the airport from the south, and descend toward the airport on an approximate heading of 345 degrees. The airplane leveled, and flew towards and then over the airport about 500 feet. The airplane then performed a missed approach, and completed a 5-mile, right-hand circuit and returned for a second attempt on the same approach. While the airplane was vectored for the second attempt, the controller asked the flight crew what the weather conditions were over the airport during the first attempt. The pilot responded, " (the clouds) were broken at 600 to 700 but we couldn't see the runway."

During the final segment of the second approach, the airplane descended and leveled at 500 feet. The last radar target was observed at 400 feet, about 1/4 mile prior to the approach end of runway 36, before radar contact was lost. The airport elevation was 168 feet.

Several witnesses employed at Freeway Airport were interviewed and provided written statements. The accounts were similar in content and detail. The airport manager stated that a pilot called about 0800 to ask about the weather at the airport. The manager responded that the ceiling at the time was 500 feet with one mile of visibility in rain. The pilot on the phone said he would attempt a landing at Freeway about 0830. A few minutes later, a gentleman arrived at the airport office and stated that he was to be picked up shortly by an airplane arriving from Warrenton, Virginia.

About 0930, a pilot announced over the UNICOM frequency that he was 5 miles from the airport, and inbound on the RNAV (GPS) Runway 36 approach. The airplane over flew the airport, and the pilot then asked over the radio if the runway lights were illuminated. The airport manager answered that the lights were on, but recommended to the pilot that he continue to Baltimore-Washington International Airport (BWI) for landing, because the "visibility was only 1/2 mile in heavy snow." The pilot did not respond.

A few minutes later, the pilot announced that he was inbound on a second approach. The airplane appeared out of the clouds over the south end of the runway, between 200 and 300 feet above the ground, and flew the length of the runway at low altitude. At the north end of the runway, the airplane turned west away from the airport, then circled to the right in a "dramatic" and "nose-high attitude" back towards the runway.

The airplane over flew the runway headed south and turned west away from the airport, as engine power increased, and the flaps were retracted. The airplane then entered a steep left bank back towards the airport and "nose-dived" out of view. Seconds later, the sounds of impact were heard.

The last passes down the runway, and the turns at each end before the final descent to the ground, were below radar coverage.

The accident occurred during the hours of daylight approximately 38 degrees, 56 minutes north latitude, and 76 degrees, 46 minutes west longitude.

Personnel information

The pilot held an airline transport pilot certificate with a rating for airplane multi-engine land. He held a commercial pilot certificate with a rating for airplane single engine land and instrument airplane. The pilot also held a flight instructor certificate with ratings for airplane single engine land, multi-engine land, and instrument airplane.

The pilot's most recent first class medical certificate was issued April 12, 2005. He reported 2,900 total hours of flight experience on that date.

The copilot held a private pilot certificate with a rating for airplane single engine land. He did not possess an instrument rating. His most recent third class medical certificate was issued February 10, 2004. Examination of his logbook revealed that the pilot had logged about 180 total hours of flight experience.

Aircraft information

The airplane was a 2001 model, with approximately 2,411 total aircraft hours. The most recent 100-hour inspection was completed February 4, 2006, at 2,401 aircraft hours.

The airplane was equipped with an IFR capable Bendix/King KLN 94 GPS receiver, and a Bendix/King KMD 540 Multi-function display. The GPS navigation database card was placarded with an effective date of April 14, 2005, and an expiration date of May 11, 2005. Due to impact damage, the GPS unit could not be adequately tested. The data card was placed in a bench-test unit, and the expiration date displayed was October 26, 2005.

According to an employee of the airplane's owner, the pilot had periodically updated the GPS data card via the Internet. A search of the manufacturer's records revealed no updates after the October 26, 2005 expiration date.

The data card for the multi-function display was effective June 14, 2001, and expired July 11, 2001.

Meteorological information

At 0941, the weather reported at Andrews Air Force Base, 9 miles southwest of Freeway Airport, included scattered clouds at 300 feet, an overcast layer at 500 feet, with 2 miles of visibility in snow and fog. The wind was from 140 degrees at 3 knots.

At 0942, the weather reported at BWI, 14 miles north of Freeway Airport, included broken clouds at 500 feet, an overcast layer at 900 feet with 3/4 mile of visibility in snow and fog. The wind was from 160 degrees at 3 knots.

Witnesses at the airport said the clouds were "on top of the trees" and that visibility was about 1/2 mile due to snow and fog.

Wreckage and impact information

The airplane was examined at the site on the day of the accident, and all major components of the airplane were accounted for at the scene. The wreckage path was oriented 035 degrees, and was approximately 90 feet long. The initial ground scar was narrow, concave, about 18 feet long, and the same approximate dimension as the leading edge of the wing. The second scar was an oval-shaped crater, about 8 feet at its widest, and 18 inches deep. The engine cowling stood next to the crater and was damaged extensively by impact. A faint, but discernable third scar ran away from the crater in line with the first scar, and ended beneath the right wing tip. The third scar was also narrow, concave, and the same approximate dimension as the leading edge of the wing.

The airplane came to rest upright on its main gear, facing opposite the direction of travel. The engine laid flat on the ground over a collapsed nose gear, and the instrument panel, cockpit and forward cabin area were destroyed by impact.

Rescue personnel separated the left wing from the airframe, and the right wing remained attached. The leading edges of both wings were crushed aft in compression outboard of the wing struts.

The aft cabin was largely intact. The roof was buckled aft of the wing box, and the fuselage was buckled aft of the main landing gear and also aft of the baggage compartment. The empennage and tail cone were largely intact. The tail section was intact.

The propeller was attached to the engine, and o

Aircraft

Registration
N3536C
Reported as
Cessna 172R
Category
Airplane
Serial number
17281034
Airframe hours
2,411.1
Engine
Lycoming IO-360-L2A, 160 horsepower, reciprocating
Damage
Destroyed
Flight
Personal · Part 91
Registered owner
Tracey Corporation
Airworthiness certificate
Standard, Normal
Last inspection
100 hour · February 1, 2005 · 9.6 hours before
Departed
W66 · Warrenton, VA
Destination
W00 · Mitchellville, MD
Flight plan
IFR
Airport
W00 · Freeway Airport, runway 36, 2,433 × 40 ft, asphalt

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.

Flight crew · 2

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
40
Injuries
Fatal
Certificates
Commercial, Flight instructor, Airline transport
Airplane ratings
Single-engine land, Multi-engine land
Instrument ratings
Airplane
Medical
Class 1, Without waivers/limitations
Last flight review
January 1, 2005
Seat
Right
Toxicology
Performed
Flight hours
2,758 total · 2,629 as pilot in command
Role
Co-pilot
Age
40
Injuries
Fatal
Certificate
Private
Airplane ratings
Single-engine land
Medical
Class 3, Without waivers/limitations
Last flight review
March 1, 2005
Seat
Left
Toxicology
Performed
Flight hours
106 total · 104 in this make and model · 21 as pilot in command

Weather

Conditions
Instrument (IMC) · Day
Wind
140° at 3 knots
Visibility
2 statute miles
Lowest ceiling
500 ft overcast
Temperature
34 °F, dew point 32 °F
Altimeter
30.10 inHg
Observed at
ADW, 9 nm away

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.