ASN Wikibase Occurrence # 138269
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information.
If you feel this information is incomplete or incorrect, you can submit corrected information.
| Date: | Monday 29 August 2011 |
| Time: | 14:27 |
| Type: |  Cessna 172M Skyhawk |
| Owner/operator: | Justice Aviation |
| Registration: | N5155Q |
| MSN: | 17261768 |
| Year of manufacture: | 1973 |
| Total airframe hrs: | 8227 hours |
| Engine model: | Lycoming O-320-E2D |
| Fatalities: | Fatalities: 0 / Occupants: 1 |
| Aircraft damage: | Substantial |
| Category: | Accident |
| Location: | Near Santa Monica Airport - KSMO, CA -
 United States of America
|
| Phase: | Approach |
| Nature: | Training |
| Departure airport: | Santa Monica, CA (SMO) |
| Santa Barbara, CA (SBA) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
The student pilot reported that shortly after liftoff, the airspeed indicator needle showed an increase and then a decrease to zero. He realized that the airplane’s airspeed indicator was not operational and advised the air traffic control tower controller. As the pilot returned to land at the airport, the airplane was higher than normal above the runway surface. With a quarter of the runway remaining, the airplane had not touched down. The air traffic control tower controller advised the pilot to go around. The pilot initiated a go-around; however, the airplane impacted trees and a house. The student pilot, as well as his flight instructor, reported that his flight instruction did not include operations simulating a loss of airspeed indication. Although the student pilot reported checking the pitot tube prior to departure, postaccident examination of the airplane’s pitot tube showed that debris, consistent with soil and insect material, was present between the ram air inlet and the drain hole. This resulted in the airspeed indicator showing zero airspeed. Review of the air traffic control services related to the accident revealed that they did not cause or contribute to the accident. The local controller’s actions were reasonable and in accordance with Federal Aviation Administration (FAA) Order 7110.65, “Air Traffic Control”: the local controller handled the situation in accordance with his best judgment based on his perceptions and understanding of the situation.
Probable Cause: The student pilot’s misjudged approach and landing attempt. Contributing to the accident was a lack of airspeed due to a blocked pitot tube.
Accident investigation:
 |
|
Sources:
NTSB
Location
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 30-Aug-2011 02:25 | gerard57 | Added |
| 30-Aug-2011 04:54 | RobertMB | Updated [Time, Aircraft type, Operator, Location, Phase, Departure airport, Destination airport, Source, Narrative] |
| 30-Aug-2011 07:28 | RobertMB | Updated [Aircraft type, Registration, Cn, Operator, Source, Narrative] |
| 21-Dec-2016 19:26 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 27-Nov-2017 17:07 | ASN Update Bot | Updated [Operator, Other fatalities, Nature, Departure airport, Destination airport, Source, Narrative] |
Corrections or additions? ... Edit this accident description
The Aviation Safety Network is an exclusive service provided by:
Quick Links:
| ASN Home | Send Correction / Feedback |
| FSF Home | Disclaimer | Copyright |
| Contact Us | Privacy Policy |
| Press / Media |
CONNECT WITH US:
©2024 Flight Safety Foundation