CEN09CA547 · Cessna 182P
Cessna 182P · Accident: loss of control on ground while standing
From Sugar Land Regional Airport (SGR) to Sugar Land Regional Airport (SGR)
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- CEN09CA547
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Cessna 182P
- Aircraft type
- Cessna 182
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N1988M
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route Narrative disagrees
- From Sugar Land Regional Airport (SGR), Sugerland, TXTo Sugar Land Regional Airport (SGR), Sugerland, TX
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Standing · engine(s) start-up
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Loss of control on ground
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Environmental issues › Physical environment
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the written statement provided by the pilot, he experienced an unexpected power surge during the engine start. The Federal Aviation Administration (FAA) reported that the airplane surged forward and the pilot was not able to arrest the forward travel. The pilot reported that he was concerned about impacting an adjacent hanger and turned the airplane left while reducing power. The airplane impacted an adjacent Piper PA-30 airplane. According to the FAA a 30-inch span of the leading edge of the right wing was crushed aft bending two ribs. An examination of the airplane, engine, and brakes revealed no anomalies.
Probable cause
The pilot's failure to control the airplane during engine startup, and his failure to maintain clearance from other objects.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN09CA547
- Event ID
- 20090827X63030
- Case number
- CEN09CA547
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 606678cd54061779059cc08d5bff7cdba3923cd3df0c4545c94f91affb2eed2e; retrieved 2026-09-15T12:51:18.460Z.