ERA22LA364 · Aerotek PITTS SPECIAL S-1S
Aerotek PITTS SPECIAL S-1S and Waco UPF-7 · Accident: ground collision during takeoff
Event
- NTSB case
- ERA22LA364
- 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
Aircraft 1 · Aerotek PITTS SPECIAL S-1S
- Aircraft type
- Aerotek PITTS SPECIAL S-1S
- 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
- N49310
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- About 40 years (built 1982)
- 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
- Takeoff
- 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
- Ground collision
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Aircraft 2 · Waco UPF-7
- Aircraft type
- Waco UPF-7
- 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
- N32141
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Pegasus Air Park (50PA), Stroudsburg, PA
- Aircraft age
- About 81 years (built 1941)
- 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
- Taxi · to runway
- 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
- Ground collision
- 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 systems
- Personnel issues › Action/decision
- Personnel issues › Psychological
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The private pilot of a predominately black and orange colored, tailwheel-equipped airplane (black airplane) reported that he was taxiing in the grass next to the turf runway 25 for departure. The taxi route required him to cross another converging turf runway 23. During the taxi, he did not make any radio calls on the airport common traffic advisory frequency (CTAF) announcing that he was taxiing or crossing runway 23. The commercial pilot of a predominately red and white colored, tailwheel-equipped airplane (red airplane) that was based at the airport stated that he was departing runway 23, which was primarily used for glider operations but also was routinely used by powered airplanes when available based on runway conditions. He scanned ahead on runway 23 and after observing there was no conflicting traffic and not hearing any announcements from other aircraft, he broadcast his intent to depart from runway 23 on the CTAF. That transmission was heard by the pilot of the black airplane but at the time it did not register to him that the red airplane was departing from a converging runway, adding that he looked along runway 25 and expected to see the red airplane departing but he did not. The pilot of the red airplane reported that just after lifting off, the right wing of his airplane and the right wing of the black airplane collided; he never saw the other airplane. Following the collision, the red airplane impacted the ground and rolled onto its right side. The pilot of the black airplane, who was taxiing slowly, reported he heard a loud engine followed immediately by the sight of something hitting his right wings.
Both airplanes sustained substantial damage to their wings during the collision. The pilots of both airplanes reported no preimpact mechanical malfunctions or failures with their airplanes that would have precluded normal operation.
According to the airport manager, the runway utilized by the pilot of the red airplane was specified in the airport facility directory to be for gliders only, though that was not strictly enforced.
Probable cause
The inability of both pilots to see and avoid the collision. Contributing to the accident was the pilot of the red airplane’s decision to utilize the converging runway for takeoff, contrary to the guidance published in the airport facility directory. Also contributing was the failure of the pilot of the black airplane to adequately utilize his radio to announce his taxi on the common traffic advisory frequency and his failure to recognize that an airplane was departing from a converging runway.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA22LA364
- Event ID
- 20220808105682
- Case number
- ERA22LA364
- 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, cause areas. 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: 6e22d5f889993c24e3d9a29de5d3ec1e2314ecf047f816635579c78826eb421b; retrieved 2026-09-13T18:38:34.589Z.