# NTSB IAD99LA022: Pitts S-2B, N340PS, Easton, MD, November 28, 1998 - Type: NTSB accident investigation - Classification: Accident · Serious injuries · Limited investigation · Final report - Date: November 28, 1998, 11:19 local (16:19 UTC) - Place: Easton, MD - Coordinates: 38.769161, -76.060661 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=38.7692&lon=-76.0607&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Highest injury: Serious injuries - Injuries: 1 serious, 1 minor, 2 uninjured - Status: Completed, report June 22, 2000 - Report: Approved by Office Director - NTSB case key (mKey): 45419 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=IAD99LA022 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/45419/pdf - Page: https://openairdocs.org/ntsb/IAD99LA022 ## Probable cause (aircraft 2) The failure of both the pilot-in-command (CFI) and dual student of the other aircraft (Pitts) to maintain adequate visual lookout. ## Probable cause (aircraft 1) The failure of both the pilot-in-command (CFI) and dual student to maintain adequate visual lookout. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Collision between aircraft (other than midair), landing - flare/touchdown - visual lookout - inadequate, pilot in command(cfi) (cause) - visual lookout - inadequate, dual student (cause) - Collision between aircraft (other than midair), landing - roll - visual lookout - inadequate, pilot of other aircraft (cause) ## Analysis (aircraft 2) The commercially rated student pilot, who was training for a tailwheel endorsement and checkout in the aircraft, was occupying the rear seat of the Pitts. The commercially rated pilot-in-command, a flight instructor, was occupying the forward seat of the Pitts. After arriving in the pattern and conducting several touch-and-go landings on runway 22, the student pilot initiated another approach as he was passing slightly downwind of the abeam position. The instructor reported making a radio call announcing 'Pitts turning base' and then, midway through the base turn, reported hearing a radio transmission from a Cessna aircraft in the pattern which was following the Pitts. Both the student and instructor reported that on final approach, the Pitts was flared for landing during which the aircraft collided with a Cessna 152 which had just landed and was preparing to clear the runway at the first taxiway. Both the student and instructor reported that they did not see the Cessna during their approach. The pilot of the Cessna following the Pitts in the pattern reported hearing the Cessna 152 call base on the airport's Unicom frequency, and described the conditions as clear and sunny. ## Analysis (aircraft 1) The commercially rated student pilot, who was training for a tailwheel endorsement and checkout in the aircraft, was occupying the rear seat of the Pitts. The commercially rated pilot-in-command, a flight instructor, was occupying the forward seat of the Pitts. After arriving in the pattern and conducting several touch-and-go landings on runway 22, the student pilot initiated another approach as he was passing slightly downwind of the abeam position. The instructor reported making a radio call announcing 'Pitts turning base' and then, midway through the base turn, reported hearing a radio transmission from a Cessna aircraft in the pattern which was following the Pitts. Both the student and instructor reported that on final approach, the Pitts was flared for landing during which the aircraft collided with a Cessna 152 which had just landed and was preparing to clear the runway at the first taxiway. Both the student and instructor reported that they did not see the Cessna during their approach. The pilot of the Cessna following the Pitts in the pattern reported hearing the Cessna 152 call base on the airport's Unicom frequency, and described the conditions as clear and sunny. ## Factual narrative (aircraft 2) On November 28, 1998, approximately 1119 eastern standard time, a Pitts S-2B, N340PS, and a Cessna 152, N5088Q, were substantially damaged during a ground collision on runway 22 at the Newnam Field airport, Easton, Maryland. The Pitts was being flown from the rear seat by a student pilot (SP) who was accompanied by a flight instructor (FI) occupying the forward seat. Both commercial pilots were uninjured. The Cessna was being flown from the left seat by a private pilot (PP) accompanied by a passenger. The pilot and passenger sustained minor and serious injuries respectively. Visual meteorological conditions prevailed and a flight plan was not filed for either aircraft. The Pitts had departed Annapolis, Maryland, approximately 1030, and was conducting practice landings at Newnam Field. The Cessna had departed Stevensville, Maryland, approximately 1100 destined for Newnam Field. The FI stated that the planned flight included practice landings at Newnam Field in anticipation of a pre-solo checkout for the commercially rated SP, and that "Results of the flights would determine whether a final checkout was going to be given to... [the SP] ...for solo of Pitts and Christen Eagle Aircraft." He also stated that the SP was "...flying rear seat with the understanding that he was piloting the aircraft and that I was assuming the role of a passenger." The FI reported that following the fourth departure, the Pitts was established on downwind and the FI "then remarked to keep an eye on the aircraft at our 1 o'clock position." This aircraft was described as being 12,000 to 15,000 feet distant and climbing northbound. The FI further reported that "absent of any radio communications from any aircraft, we announced `Pitts turning base for runway 22 at Easton, doing a touch and go.' Midway through our base leg there was a transmission, as I recall that said `Cessna turning downwind to base, Easton, runway 22. I immediately responded that the Pitts was on base...'" The FI described the approach as turning base to final at 500 feet and approximately 1,500 to 2,000 feet from the approach end of the runway. Power was adjusted, the aircraft was flared, and airspeed was allowed to bleed off. The FI reported that "suddenly, I saw a white wing in my sight off the right side of the nose of the aircraft. We hit immediately before any evasive action could be taken." The FI also stated that "at no time did we hear any radio transmission from the aircraft we collided with or did we observe it on the final approach path when we were on downwind or base leg" (refer to attached NTSB Form 6120.1/2 and STATEMENT FI-I). The SP stated that "I required training from... [the IP] ...so that I could obtain a logbook endorsement to operate tailwheel aircraft and also to become familiar with the operating characteristics of Pitts type aircraft." The SP reported that several landings were made on runway 22 and recalled "at least one other aircraft in the traffic pattern made a position report while we were in the landing pattern setting up for the accident landing." He further stated that on the accident landing "a left turn to base leg was made slightly past a position opposite the approach end of runway 22" and that the IP "...transmitted our position on the Unicom frequency." He further reported that "a wings level base leg was flown. I distinctly recall looking left for aircraft approaching the runway, as well as checking to see if the runway was clear, and I also looked to the right for aircraft on final. I did not see any aircraft." The SP continued reporting that "as we became established on final for runway 22, I did not see any aircraft in front of the Pitts S-2B or on the runway. Upon reaching the point where a normal flare for landing is commenced, the power was reduced to idle and the flare maneuver commenced. While in the flare, the white wing of a Cessna suddenly appeared out of the right side of the canopy" (refer to attached NTSB Form 6120.1/2 and STATEMENT SP-I). The pilot of the Cessna (PP) was interviewed by an inspector from the Federal Aviation Administration's (FAA) Baltimore Flight Standards District Office (FSDO) and reported that he had just landed on runway 22 with the intention of exiting at the first taxiway. He reported that he was decelerating to about 10 miles per hour when his aircraft was impacted from behind (refer to attached STATEMENTS PP-I and PP-II). A private pilot, who was interviewed by an inspector from the FAA's Baltimore FSDO, reported that while he was awaiting departure from runway 22 he witnessed the approaching aircraft and subsequent accident. He reported that he "saw a Cessna turning base where most people turn base, over the golf course. He turns final and, about the time he gets to short final, here comes this Pitts on a very close base." The witness further described the Pitts' location reporting that "when he was on base, he was headed towards the traffic lights on route fifty." He also reported that "when he [the Pitts] turned final, the Cessna was in front of him, probably just landing and just to the right of him" (refer to STATEMENT W-I and CHART I). A commercial flight instructor, who was interviewed by an inspector from the FAA's Baltimore FSDO, reported that "as we departed runway 22 and joined the downwind leg, we heard 88Q [the Cessna] call base, and observed the aircraft during this time, extending our downwind slightly to give proper spacing. At no time since departing the runway did we see the Pitts in the pattern." The instructor and his student subsequently heard a radio transmission of the accident and executed a go-around (refer to STATEMENT W-II). A third witness working in the airport's terminal building, and who was interviewed by an inspector from the FAA's Baltimore FSDO, reported observing the Cessna 152 land on runway 22. She reported that the Pitts then came by "fast and low" and the Pitts hit the Cessna. In a subsequent interview with the same inspector, she recalled "hearing the Cessna's [sic] broadcast and was asked `Do you recall hearing the Pitts making any radio transmissions?' She responded `No, I don't'" (refer to STATEMENT W-III(a) and (b)). A flight instructor who witnessed the accident reported the environmental conditions as "clear, sunny" and further stated that "both occupants were wearing headsets that I observed during one of their landings." The aircraft collided near the centerline of runway 22 and approximately 200 feet short of the first taxiway exit to the ramp area (refer to CHART I and DIAGRAM I). ## Factual narrative (aircraft 1) On November 28, 1998, approximately 1119 eastern standard time, a Pitts S-2B, N340PS, and a Cessna 152, N5088Q, were substantially damaged during a ground collision on runway 22 at the Newnam Field airport, Easton, Maryland. The Pitts was being flown from the rear seat by a student pilot (SP) who was accompanied by a flight instructor (FI) occupying the forward seat. Both commercial pilots were uninjured. The Cessna was being flown from the left seat by a private pilot (PP) accompanied by a passenger. The pilot and passenger sustained minor and serious injuries respectively. Visual meteorological conditions prevailed and a flight plan was not filed for either aircraft. The Pitts had departed Annapolis, Maryland, approximately 1030, and was conducting practice landings at Newnam Field. The Cessna had departed Stevensville, Maryland, approximately 1100 destined for Newnam Field. The FI stated that the planned flight included practice landings at Newnam Field in anticipation of a pre-solo checkout for the commercially rated SP, and that "Results of the flights would determine whether a final checkout was going to be given to... [the SP] ...for solo of Pitts and Christen Eagle Aircraft." He also stated that the SP was "...flying rear seat with the understanding that he was piloting the aircraft and that I was assuming the role of a passenger." The FI reported that following the fourth departure, the Pitts was established on downwind and the FI "then remarked to keep an eye on the aircraft at our 1 o'clock position." This aircraft was described as being 12,000 to 15,000 feet distant and climbing northbound. The FI further reported that "absent of any radio communications from any aircraft, we announced `Pitts turning base for runway 22 at Easton, doing a touch and go.' Midway through our base leg there was a transmission, as I recall that said `Cessna turning downwind to base, Easton, runway 22. I immediately responded that the Pitts was on base...'" The FI described the approach as turning base to final at 500 feet and approximately 1,500 to 2,000 feet from the approach end of the runway. Power was adjusted, the aircraft was flared, and airspeed was allowed to bleed off. The FI reported that "suddenly, I saw a white wing in my sight off the right side of the nose of the aircraft. We hit immediately before any evasive action could be taken." The FI also stated that "at no time did we hear any radio transmission from the aircraft we collided with or did we observe it on the final approach path when we were on downwind or base leg" (refer to attached NTSB Form 6120.1/2 and STATEMENT FI-I). The SP stated that "I required training from... [the IP] ...so that I could obtain a logbook endorsement to operate tailwheel aircraft and also to become familiar with the operating characteristics of Pitts type aircraft." The SP reported that several landings were made on runway 22 and recalled "at least one other aircraft in the traffic pattern made a position report while we were in the landing pattern setting up for the accident landing." He further stated that on the accident landing "a left turn to base leg was made slightly past a position opposite the approach end of runway 22" and that the IP "...transmitted our position on the Unicom frequency." He further reported that "a wings level base leg was flown. I distinctly recall looking left for aircraft approaching the runway, as well as checking to see if the runway was clear, and I also looked to the right for aircraft on final. I did not see any aircraft." The SP continued reporting that "as we became established on final for runway 22, I did not see any aircraft in front of the Pitts S-2B or on the runway. Upon reaching the point where a normal flare for landing is commenced, the power was reduced to idle and the flare maneuver commenced. While in the flare, the white wing of a Cessna suddenly appeared out of the right side of the canopy" (refer to attached NTSB Form 6120.1/2 and STATEMENT SP-I). The pilot of the Cessna (PP) was interviewed by an inspector from the Federal Aviation Administration's (FAA) Baltimore Flight Standards District Office (FSDO) and reported that he had just landed on runway 22 with the intention of exiting at the first taxiway. He reported that he was decelerating to about 10 miles per hour when his aircraft was impacted from behind (refer to attached STATEMENTS PP-I and PP-II). A private pilot, who was interviewed by an inspector from the FAA's Baltimore FSDO, reported that while he was awaiting departure from runway 22 he witnessed the approaching aircraft and subsequent accident. He reported that he "saw a Cessna turning base where most people turn base, over the golf course. He turns final and, about the time he gets to short final, here comes this Pitts on a very close base." The witness further described the Pitts' location reporting that "when he was on base, he was headed towards the traffic lights on route fifty." He also reported that "when he [the Pitts] turned final, the Cessna was in front of him, probably just landing and just to the right of him" (refer to STATEMENT W-I and CHART I). A commercial flight instructor, who was interviewed by an inspector from the FAA's Baltimore FSDO, reported that "as we departed runway 22 and joined the downwind leg, we heard 88Q [the Cessna] call base, and observed the aircraft during this time, extending our downwind slightly to give proper spacing. At no time since departing the runway did we see the Pitts in the pattern." The instructor and his student subsequently heard a radio transmission of the accident and executed a go-around (refer to STATEMENT W-II). A third witness working in the airport's terminal building, and who was interviewed by an inspector from the FAA's Baltimore FSDO, reported observing the Cessna 152 land on runway 22. She reported that the Pitts then came by "fast and low" and the Pitts hit the Cessna. In a subsequent interview with the same inspector, she recalled "hearing the Cessna's [sic] broadcast and was asked `Do you recall hearing the Pitts making any radio transmissions?' She responded `No, I don't'" (refer to STATEMENT W-III(a) and (b)). A flight instructor who witnessed the accident reported the environmental conditions as "clear, sunny" and further stated that "both occupants were wearing headsets that I observed during one of their landings." The aircraft collided near the centerline of runway 22 and approximately 200 feet short of the first taxiway exit to the ramp area (refer to CHART I and DIAGRAM I). ## Aircraft 1 - Registration: [N340PS](https://openairdocs.org/aircraft/N340PS), registered now, S/N 5338 (OpenAirDocs) - Reported make and model: Pitts S-2B - Registry model: [Aviat PITTS S-2B](https://openairdocs.org/model/aviat-pitts-s-2b) (registry code 2210308) (OpenAirDocs) - Registry engine: [Lycoming AEIO-540 series](https://openairdocs.org/engine/lycoming-aeio-540-series) (registry code 41568, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 5338 - Airframe hours: 189 - Engines: Lycoming AEIO-540-D4A5 260 horsepower reciprocating - Damage: Substantial damage - Flight: Instructional, Part 91 - Registered owner: Dent Air Inc - Airworthiness certificate: Standard, Normal; Standard, Aerobatic - Last inspection: 100 hour, November 9, 1998, 74 hours before - Departed: ANP, ANNAPOLIS, MD - Destination: ESN - Airport: ESN, Easton/Newnam Field, runway 22, 5,511 × 100 ft, asphalt ## Aircraft 2 - Registration: [N5088Q](https://openairdocs.org/deregistered/N5088Q-1999-07-27), registration cancelled 1999-07-27, S/N 15285070 (OpenAirDocs) - Reported make and model: Cessna 152 - Registry model: [Cessna 152](https://openairdocs.org/model/cessna-152) (registry code 2071835) (OpenAirDocs) - Category: Airplane - Serial number: 15285070 - Airframe hours: 6841 - Engines: Lycoming O-235 115 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Registered owner: Aero Source Inc - Airworthiness certificate: Standard, Utility - Last inspection: 100 hour, November 25, 1998, 2 hours before - Departed: W29, STEVENSVILLE, MD - Destination: ESN - Airport: ESN, Easton/Newnam Field, runway 22, 5,511 × 100 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot, aircraft N340PS; age 61; flight instructor, commercial; airplane ratings: single-engine land, multi-engine land, single-engine sea; instrument ratings: airplane; medical: class 2, valid medical--no waivers/lim.; seat: front; flight hours: 6,199 total, 4,000 in this make and model, 5 in the last 24 hours - Pilot, aircraft N5088Q; age 49; private; airplane ratings: single-engine land; medical: class 3, valid medical--no waivers/lim.; seat: left; flight hours: 419 total, 62 in this make and model, 380 as pilot in command, 12 in the last 90 days, 12 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: 240° at 10 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 61 °F, dew point 28 °F - Altimeter: 30.00 inHg - Observed at: SBY, 38 nm away ## FAA reports on this event (2) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 19981128032401A](https://openairdocs.org/incident/19981128032401A), Nov 28, 1998: Aviat PITTSS2B, Easton, MD, Substantial damage. Acft landed and struck N5088Q, which was still on runway. (.19) on November 28, 1998, at 1115 eastern standard time, a pitts S-2B, N340PS, and a Cessna 152,… - [Accident 19981128032402A](https://openairdocs.org/incident/19981128032402A), Nov 28, 1998: Cessna 152, Easton, MD, Substantial damage. The pilot of Cessna 152 aircraft N5088Q, landed on runway 22 at Easton airport (esn), Easton, Maryland. The flying pilot of N340PS (a pitts S-2B aircraft)… From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.