Sponsor Message:
Aviation Technical / Operations Forum
My Starred Topics | Profile | New Topic | Forum Index | Help | Search 
Martinair 767 With Gremlins To BOS..any More Info?  
User currently offlineEksath From United States, joined Aug 2004, 786 posts, RR: 29
Posted (5 years 2 months 4 weeks 10 hours ago) and read 1420 times:



http://aviation-safety.net/database/1996/960528-0.htm

Any of you guys heard what the final analysis was for this flight?...Was it the "numerous PEDs in use?"


View Large View Medium
Click here for bigger photo!

Photo © Mark Garfinkel



Prior to departure, the flight crew noted anomalies with the airplane clocks. Once corrected, they proceeded with the flight. En route, the airplane experienced numerous electrical anomalies where various warning lights would illuminate, and then extinguish. These occurrences were also accompanied by uncommanded auto-pilot disconnects, changes in airplane zero fuel weight, as displayed on the control display unit (CDU) of the flight management system (FMS), and the blanking of transponder codes. The flight crew, in radio contact with their dispatch center, discussed the situation and agreed that they could continue with the flight. The Boeing Aircraft Company through the Martinair dispatch center supplied technical assistance. A check of the passenger cabin revealed that numerous personal electronic devices (PEDs) were in use. They were requested to be turned off. At one time while over the North Atlantic, there was a period of time when no anomalies occurred. Nearing the North American continent, and with additional anomalies occurring, the flight crew initially planned to divert to Newark, New Jersey. As the electrical anomalies continued, additional systems were affected, and a decision was made to divert to Boston, Massachusetts. Following the decision to divert, there were failures of the co-pilots electronic attitude director indictors (EADI), and electronic horizontal situation indicators (EHSI). Navigation was lost to the captain's EHSI.
During the initial descent into Boston, the aircraft was flown manually due to autothrottle disengagement and multiple A/P disengagements. When the airplane was configured with flaps 1 (slat extension, no trailing edge flaps), the two needles on a cockpit gauge which represented the respective wing slat positions disagreed. The flight crew checked the runway required for landing with zero flaps, and the runway available at Boston. With sufficient runway available, the captain in concert with the other crew member decided to make no more configuration changes, resulting in a leading edge slat only approach speed of 162 knots, Flap problems had been expected by the crew based on the previous events. The slats were visually inspected to be extended. In the cabin the seatbelts signs switched on and off uncommanded.
During the last portion of flight, the Engine Indicating and Crew Alerting System (EICAS) was filled with caution and advisory messages which were read by F/O 2 from the observers seat on request of the captain.
Although no identification could be received from the Instrument Landing System (ILS), the indication on the left Attitude Director Indicator (ADI) and on the standby ADI seemed valid. On final approach to Boston, numerous warning lights illuminated, extinguished, and other warning lights illuminated.
After touch down reverse thrust and autospeedbrakes were not available. Manual braking was anticipated since the autobrake selector did not latch. Braking was done manually by the captain while the wing spoilers were extended by the F/O 1. Just after touch-down the captain initially used full manual braking. The cabin crew's observations were as if they were riding on gravel (pebbles), and the cockpit crew suspected tire failures just after turning off the runway. The last high speed turn off to the left was taken to vacate runway 4R, on which the airplane was brought to a stop. The pilots reported to feel no effect from the manually selected ground spoilers. In the meantime all main landing gear tires were blown or deflated and the airplane was brought to a stop without fully vacating the runway. A small wheel brake fire developed after landing and was immediately extinguished by the airport fire fighting personnel


World Wide Aerospace Photography
6 replies: All unread, jump to last
 
User currently offlineSATL382G From , joined Dec 1969, posts, RR:
Reply 1, posted (5 years 2 months 4 weeks 9 hours ago) and read 1362 times:

Took about 20 seconds to find at NTSB web site....

Please check there next time....

Poor connection at battery.

http://www.ntsb.gov/ntsb/brief.asp?ev_id=20001208X05844&key=1

SATL382G

User currently offlineEksath From United States, joined Aug 2004, 786 posts, RR: 29
Reply 2, posted (5 years 2 months 4 weeks 7 hours ago) and read 1254 times:

SATL382G,

Thanks.

Eksath


World Wide Aerospace Photography
User currently offlineSATL382G From , joined Dec 1969, posts, RR:
Reply 3, posted (5 years 2 months 4 weeks 1 hour ago) and read 1200 times:

No prob..

Kind of interesting going back to read this. I didn't know the airplane was returned to service with test instrumentation installed or that similar problems were found on airplanes still on the production line at Everett. woohoo!

SATL382G

User currently offlineTappan From United States, joined Oct 1999, 1527 posts, RR: 53
Reply 4, posted (5 years 2 months 2 weeks 4 days 13 hours ago) and read 1020 times:

Thanks for the great explanation.....I am the photographer of this "flat tires/MartinAir" photo....
Mark Garfinkel

User currently offlineSATL382G From , joined Dec 1969, posts, RR:
Reply 5, posted (5 years 2 months 2 weeks 4 days 12 hours ago) and read 1005 times:

Great Pix! How did you get it?

User currently offlineEMBQA From United States, joined Oct 2003, 8426 posts, RR: 19
Reply 6, posted (5 years 2 months 2 weeks 4 days 12 hours ago) and read 1005 times:

I was trying to land at BOS when this occurred. As we flew over to start our approach, it was still out on the runway, but by the time we landed and taxied up to terminal C she was being towed by on its way to North Cargo. Sadly I was flying back from a 3 week duty cover our Line MX base at JFK. It was a few weeks later that TWA 800 went down. The hotel we had used was the same hotel the victim's families had been placed in. The guy that replaced me said it was the most solemn and sad place he had ever seen.

[Edited 2004-09-20 02:31:45]


"It's not the size of the dog in the fight, but the size of the fight in the dog"
Top Of Page
Forum Index

Reply To This TopicMartinair 767 With Gremlins To BOS..any More Info?
Username: 


No username? Sign up now!
  • Tech/Ops related posts only!
  • Not Tech/Ops related? Use the other forums
  • No adverts of any kind. This includes web pages.
  • No hostile language or criticizing of others.
  • Do not post copyright protected material.
  • Use relevant and describing topics.
  • Check if your post already been discussed.
  • Check your spelling!           DETAILED RULES (NEW)
  • Password: 


    Forgot Password? Be reminded.
    Remember me on this computer (uses cookies)

    Add Images Add SmiliesPosting Help
    FORUM RULES HAVE CHANGED - READ THEM HERE

    Please check your spelling (press "Check Spelling" above)


    Similar topics:More similar topics...
    A380 Delay Linked With Cu To Al Wiring Switch? posted Sat Sep 16 2006 16:29:43 by Art
    Line Of Sight With Regard To Altitude posted Fri Dec 9 2005 21:06:53 by THVGJP
    UAL- how can I find out more info about their flights posted Thu Nov 4 2004 18:40:35 by Cpn360
    Any 767-200 With RR Engines? posted Wed Nov 23 2005 23:07:58 by Socal
    Hard To Get Industry Info? posted Thu Aug 31 2006 21:52:58 by 3DPlanes
    How To Deal With Air Sickness posted Fri Aug 4 2006 06:14:07 by AAden
    757 And 767 RB211 Is There Any Difference In Size? posted Mon Jun 19 2006 14:38:00 by Edumotoki
    Was The P&W 2000 Meant To Compete With The CFM-56? posted Mon May 29 2006 19:31:12 by 747400sp
    Any Aircraft Equipped With FADEC? posted Tue Apr 11 2006 04:36:03 by Spikebe90
    757 To 767 Mx Conversion Training posted Sun Mar 26 2006 11:05:32 by HAWK21M

    Sponsor Message:
    Printer friendly format