Back to Search

MCR-01, G-TBEE, 2 October 2005

Air Accidents (AAIB)

Published on 10 December 2014, 21:20

Summary
aircraft category
general-aviation-fixed-wing
aircraft type
MCR-01
bulk published
1
date of occurrence
2005-10-02
location
Near Lymington, Hampshire
registration
G-TBEE
report type
field-investigation

Report Overview

MCR-01, G-TBEE

Summary:

The aircraft was flying a route which took it along the north shore of the western Solent when the accident occurred. Within minutes of the pilot’s last transmission to ATC, and without any indication that he was experiencing a problem, the aircraft deviated from its course and descended to low level in the vicinity of the town of Lymington in an apparent attempt to land. Whilst manoeuvring at low level the aircraft was seen to pitch up and depart from controlled flight before descending steeply to the ground. The technical examination eliminated mechanical or structural failure as a cause of the accident but concluded that a partial engine failure may have contributed to it. Post mortem results raised the possibility that the pilot may have been medically incapacitated prior to the accident itself.

This overview has been truncated. Please refer to the official documents below for the complete canonical report.

Official Documents

Document Content Preview

Extracted text from the first few pages of the official documents.

MCR-01, G-TBEE 06-06.pdf

92 © Crown copyright 2006 AAIB Bulletin: 6/2006 G-TBEE EW/C2005/10/01 ACCIDENT Aircraft Type and Registration: MCR-01, G-TBEE No & Type of Engines: 1 Rotax 912 ULS piston engine Year of Manufacture: 2000 Date & Time (UTC): 2 October 2005 at 1159 hrs Location: Near Lymington, Hampshire Type of Flight: Private Persons on Board: Crew - 1 Passengers - 1 Injuries: Crew - 1 (Fatal) Passengers - 1 (Fatal) Nature of Damage: Aircraft destroyed Commander’s Licence: Private Pilot’s Licence Commander’s Age: 53 years Commander’s Flying Experience: 1059 hours (estimated - of which 290 were on type) Last 90 days - 8:30 hours estimated Last 28 days - 6:30 hours estimated Information Source: AAIB Field Investigation Synopsis The aircraft was flying a route which took it along the north shore of the western Solent when the accident occurred. Within minutes of the pilot’s last transmission to ATC, and without any indication that he was experiencing a problem, the aircraft deviated from its course and descended to low level in the vicinity of the town of Lymington in an apparent attempt to land. Whilst manoeuvring at low level the aircraft was seen to pitch up and depart from controlled flight before descending steeply to the ground. The technical examination eliminated mechanical or structural failure as a cause of the accident but concluded that a partial engine failure may have contributed to it. Post mortem results raised the possibility that the pilot may have been medically incapacitated prior to the accident itself. History of the flight The pilot had intended to fly from Shoreham Airport in Sussex where the aircraft was based, to Dunkeswell Airfield in Devon where a ‘fly in’ event was being held. The pilot was accompanied by a passenger with whom he had flown on numerous occasions. There were other aircraft owners present in the vicinity during the pilot’s pre-flight preparations, some of whom spoke to the pilot, though none described anything unusual until the point of engine start. One of those present recalled that, at that point, G-TBEE’s engine was started but then shut down again after a short while. It appeared to be a normal shutdown, without faltering. The engine was started again and the aircraft taxied to the fuel pumps, arriving there at 1116 hrs. 93 © Crown copyright 2006 AAIB Bulletin: 6/2006 G-TBEE EW/C2005/10/01 There was CCTV coverage of the refuelling area which was made available for the investigation. The pilot initially requested 40 ltr of Avgas 100LL, but subsequently revised his requirement to 35 ltr. The refuelling supervisor recalled nothing unusual about the fuelling process or the aircraft’s two occupants. However, the pilot did not start the engine and taxi immediately after completion of the fuelling paperwork. Instead he manhandled G-TBEE to the edge of the refuelling area where he and the passenger boarded the aircraft, and sat with the canopy open for some 5 minutes before eventually starting the engine and taxiing away. The aircraft taxied to the holding point of Runway 02. A Cessna aircraft was also at the holding point and its pilot, who was familiar with G-TBEE and its owner, saw G-TBEE but did not recall seeing anything unusual about the aircraft. The Cessna departed first and headed west from Shoreham, and G-TBEE took off 3 minutes later at 1135 hrs. As the Cessna was flying west at 2,000 ft, G‑TBEE overtook it on its right hand side at the same height with a separation of about 200 m. When G-TBEE had drawn ahead of the Cessna, it was seen to rock its wings in a pronounced manner, which the Cessna pilot took to be an acknowledgement by the pilot of G-TBEE that he had seen his aircraft. As G‑TBEE was rocking its wings, the Cessna pilot saw it pitch up suddenly and briefly before recovering again to level flight. The pitch‑up appeared to be the result of a deliberate control input. The extent or duration of the pitch-up was insufficient to cause a marked change of height, but was regarded as unusual by the Cessna pilot. G-TBEE then continued on a westerly track which took it close to Chichester and overhead Portsmouth. The pilot made routine radio contact with Goodwood Airfield at 1142 hrs, and reported that he was maintaining 3,000 ft amsl. At 1152 hrs the pilot contacted Solent Radar, based at Southampton Airport; at this time he was overhead Gosport and flying at a reported 2,300 ft amsl. The pilot declared that he was routing to Calshot then Sandbanks; both are visual reporting points, located near the entrances to Southampton Water and Poole Harbour respectively. The pilot requested, and was given, a Flight Information Service (FIS) and advised that he would have to be below 2,000 ft when passing abeam Calshot in order to remain below controlled airspace. G-TBEE was seen from another aircraft as it flew past the entrance to the Beaulieu River and appeared to be flying normally in straight and level flight. At 1157 hrs the pilot reported that he was abeam Calshot at 1,300 ft amsl and was instructed to contact Bournemouth Radar. The pilot acknowledged the frequency change, but no further radio calls were received from the aircraft, either on the new Bournemouth frequency or the Solent Radar frequency. The aircraft’s radio was found after the accident to be selected to the Bournemouth frequency. Although several witnesses reported seeing the aircraft in a steep descent, the ground impact was not seen and none of the witnesses realised that the aircraft had crashed. The wreckage was discovered in a field nearly an hour later by the land owner who contacted the emergency services at 1305 hrs. The fire brigade arrived on scene at 1312 hrs, followed a few minutes later by the ambulance service. Both occupants of the aircraft had sustained immediately fatal injuries. GPS derived information (see Figure 1) G-TBEE was equipped with a GPS navigation system that recorded the time, position, groundspeed, track and GPS altitude every 30 seconds during the flight. GPS altitude can be subject to substantial error but the recorded values suggested that for much of the flight, where the aircraft had apparently been flown approximately level, 94 © Crown copyright 2006 AAIB Bulletin: 6/2006 G-TBEE EW/C2005/10/01 the GPS altitude had been accurate to within ±100 ft. Data from the GPS showed that the aircraft flew a steady track of about 255º(M) which took it along the north shore of the western Solent towards Lymington, flying at between 124 kt and 129 kt ground speed. The GPS data showed that, at the time the pilot made his last confirmed radio transmission, the aircraft was actually 3 nm west-south‑west of Calshot, and only 1.5 nm from the accident site, the lateness of this transmission having been caused by the Solent frequency being blocked for a while with other transmissions. At about the time of this transmission from G-TBEE, and about 2 minutes before the estimated time of the accident, the data from the GPS showed deviations from the previous steady state. The GPS altitude first showed a dip to 1,153 ft, and then the next point, 30 seconds later was recorded as being 1,318 ft (Position A, Figure 1). Both of these values were outside the narrow height band within which the aircraft had been flying during the few minutes since the aircraft had completed the descent requested by ATC. Point A was the last recorded point on the aircraft’s original track. The next and penultimate point (B) showed a GPS altitude of 1,234 ft and a reduced groundspeed of 95 kt. The average rate of descent from A to B was less than 200 ft per minute (ft/min), though this increased to about 1,400 ft/min between B and C. The next and final recorded point was 800 m from the previous, and almost due north of it, though the aircraft’s track at this stage was just south of west, similar to that of the previous position. Groundspeed at C was 80 kt and the recorded GPS altitude was 513 ft. Based on the position A 1318ft

Text truncated. The original document has 15 pages.

Read the full text here

Change History

  • First published.

Related Entities

Search the database for other reports involving these entities.