NYC07FA126 · Columbia Aircraft Mfg LC42-550FG
Columbia Aircraft Mfg LC42-550FG · Accident: loss of control in flight during landing
From Albert Whitted Airport (SPG) to Mountain Air Airport (2NC0)
Narrative check · The NTSB narrative appears to contradict this record's aircraft involved. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- NYC07FA126
- 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
- 3 · 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
Columbia Aircraft Mfg LC42-550FG Possible conflict
- Aircraft type
- Columbia LC42
- 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
- N2537A
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Albert Whitted Airport (SPG), St. Petersburg, FLTo Mountain Air Airport (2NC0), Burnsville, NC
- 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
- Landing · flare/touchdown
- First occurrenceThe 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 in flight
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Recovery from bounced landing, improper
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot was attempting to land at an airport that was located on the top of a mountain, and the single runway was 2,875 feet long by 50 feet wide. The airplane approached runway "high and fast," touched down within the first third, and bounced about 10 to 20 feet above the surface. The airplane bounced again about 300 feet further down the runway, in a 20- to 30-degree nose up attitude, and with the speed brakes deployed. The airplane then veered left of the runway centerline, and the engine sound increased to "full power." As the airplane headed toward an embankment off the left side of the runway, it rolled right, and the right wing tip scraped the runway. After traveling up the embankment, the airplane turned back toward the runway, crossed it, and struck four parked airplanes. A post-impact fire consumed the accident airplane, and two of the four parked airplanes. Examination of the wreckage identified no preimpact mechanical anomalies, and there were not notable medical anomalies associated with the pilot.
Probable cause
The pilot's improper recovery from a bounced landing resulting in a loss of directional control and subsequent impact with several parked airplanes.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC07FA126
- Event ID
- 20070531X00672
- Case number
- NYC07FA126
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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, coordinates. 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: 4498464aa4522c7d17af63c287b8fe1008465c9ed1cdc5b0921f8101fbc65aa3; retrieved 2026-09-20T16:35:40.498Z.