B737

From SKYbrary Wiki

Article Information
Category:	Aircraft Types
Content source:	SKYbrary
Content control:	EUROCONTROL

B737
Name	737-700
Manufacturer	BOEING
Body	Narrow
Type	Fixed Wing
WTC	Medium
APC	C
Engine	Jet
Engine count	Multi
Also manufacturered as: BOEING Clipper BOEING C-40 Clipper BOEING C-40 BOEING 737-700 BOEING BBJ BOEING 737-700 BBJ

BOEING 737-700

Image source: IANS

Description

Short to medium range airliner. In service since 1997. Standard version of the BOEING 737 next generation. All versions have more powerful and efficient engines, improved wings and tail sections and modernized cockpits. Replaced the BOEING 737-300. BBJ 1 long range corporate version with fuselage of 737-700 and wings of 737-800. With winglets the aircrafts wingspan is 35.79 meters. The B737 is member of the B737 family of aircraft.

General

Aircraft name	737-700
ICAO code/WTC	B737 / M
Manufacturer	BOEING
Type Code/APC	L2J / C

Technical Data

Wing span	34.3 m112.533 ft
Length	33.6 m110.236 ft
Heigth	12.6 m41.339 ft
Powerplant	2 x 89 kN CFM56-7 or 2 x 107 kN CFM56-7HGW turbofans.
Engine Model	CFM International CFM56

For further details consult EUROCONTROL Aircraft Performance Database:

• BOEING 737-700

Accidents & Serious Incidents involving B737

• A319 / B737, Zurich Switzerland, 2002 (RI HF) (On 23 November 2002, an A319, landing on Rwy16 at Zurich Switzerland, narrowly missed collision with a B737 cleared for take off on an intersecting runway.)
• B737 / F100, Geneva Switzerland, 2006 (HF LOS) (On 29 December 2006, take off clearance for an Easyjet B737-700 which had been lined up ready for a night departure from Geneva was delayed whilst a business jet which had just landed cleared the runway. Take off clearance was given when further landing traffic, A KLM Cityhopper F100, was at IMC at a range from touchdown of 2nm finals. When the F100 became visual at 350 ft agl, the flight crew did not notice the accelerating B737 on the runway. As the B737 was nearing V1, ATC cancelled the take off clearance and instructed the F100 to make a non standard missed approach involving a turn off the runway extended centreline. The B737 continued the take off, subsequently advising that it had been considered inappropriate to make the high speed rejected take off which would have been required.)
• B737 en-route, Glen Innes Australia, 2007 (AW HF) (On 17 November 2007 a Boeing 737-700 being operated by Virgin Blue on a scheduled passenger service from Coolangatta to Melbourne at night experienced a right hand engine bleed trip off during the take off, which was continued. A subsequent attempt at reset was not successful and once above FL170, above which APU air use was not permitted, only the left engine bleed air would be available for air conditioning and cabin pressurisation. The flight crew initially decided to cruise at a lower level than planned, FL250, but once there, icing conditions were encountered and the crew decided to continue the climb to FL350 to cruise clear of cloud.)
• B737, Amsterdam Netherlands, 2003 (GND HF) (n 22 December 2003, a Boeing 737-700 being operated by UK Operator Easyjet on a scheduled passenger flight from Amsterdam to London Gatwick was taxiing for departure at night in normal visibility and took a different route to that instructed by ATC. The alternative route was, unknown to the flight crew, covered with ice and as a consequence, an attempt to maintain directional control during a turn was unsuccessful and the aircraft left wing collided with a lamp-post. The collision seriously damaged the aircraft and the lamp post. One passenger sustained slight injuries because of the impact. The diagram below taken from the official investigation report shows the area where the collision occurred.)
• B737, Chicago Midway IL, USA 2011 (RE HF) (On 26 April 2011 a Southwest Boeing 737-700 was assessed as likely not to stop before the end of landing runway 13C at alternate Chicago Midway in daylight and was intentionally steered to the grass to the lef of the runway near the end, despite the presence of a EMAS. The subsequent investigation determined that the poor deceleration was a direct consequence of a delay in the deployment of both speed brakes and thrust reverser. It was noted that the crew had failed to execute the ‘Before Landing’ Checklist which includes verification of speed brake arming.)
• … further results