Boeing 767-300: Difference between revisions

From FlightGear wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 15: Line 15:
= The Boeing 767-300 =
= The Boeing 767-300 =


The '''767-300''' is a lengthened 767 ordered by Japan Airlines in 1983. It first flew on January 30, 1986, and was delivered to JAL on September 25.
The '''767-300''' is a lengthened [[Boeing 767|767]] ordered by Japan Airlines in 1983. It first flew on January 30, 1986, and was delivered to JAL on September 25.
The 767-300's direct competitor from [[Airbus]] is the [[Airbus A330-200|A330-200]]. The 767-300 is expected to be replaced by the [[Boeing 787-800|787-8]] in Boeing's lineup. As of August 2009, total orders for the 767-300/300ER/300F stand at 749 with 690 delivered. This includes 104 orders (all delivered) for the -300, 563 orders for the -300ER (535 delivered), and 82 orders for the -300F (51 delivered). A total of 661 Boeing 767-300/-300ER/-300F aircraft were in airline service as of July 2009.
The 767-300's direct competitor from [[Airbus]] is the [[Airbus A330-200|A330-200]]. The 767-300 is expected to be replaced by the [[Boeing 787-800|787-8]] in Boeing's lineup. As of August 2009, total orders for the 767-300/300ER/300F stand at 749 with 690 delivered. This includes 104 orders (all delivered) for the -300, 563 orders for the -300ER (535 delivered), and 82 orders for the -300F (51 delivered). A total of 661 Boeing 767-300/-300ER/-300F aircraft were in airline service as of July 2009.



Revision as of 05:13, 30 October 2009

This article describes content/features that may not yet be available in the latest stable version of FlightGear (2020.3).
You may need to install some extra components, use the latest development (Git) version or even rebuild FlightGear from source, possibly from a custom topic branch using special build settings: .

This feature is scheduled for FlightGear (unknown). 10}% completed

If you'd like to learn more about getting your own ideas into FlightGear, check out Implementing new features for FlightGear.


Boeing 767-300
767-300 factory01.png
Type Airliner
Author(s) Isaias V. Prestes and Liam
FDM JSBSim
--aircraft= 767-300
Status Alpha

The Boeing 767-300

The 767-300 is a lengthened 767 ordered by Japan Airlines in 1983. It first flew on January 30, 1986, and was delivered to JAL on September 25. The 767-300's direct competitor from Airbus is the A330-200. The 767-300 is expected to be replaced by the 787-8 in Boeing's lineup. As of August 2009, total orders for the 767-300/300ER/300F stand at 749 with 690 delivered. This includes 104 orders (all delivered) for the -300, 563 orders for the -300ER (535 delivered), and 82 orders for the -300F (51 delivered). A total of 661 Boeing 767-300/-300ER/-300F aircraft were in airline service as of July 2009.


Completed/In progress

The aircraft development was started at 10/29/2009.

767-300 3D model at 3D editor
767-300 3D model at 3D editor
Thompson livery by Liam
Thompson livery by Liam

Completed

  • Models - for 3D models
  • Splashs - for aircraft specific splash screens (tempoarary)
  • UVmap - for 3D models
  • Texture - for 3D models
  • Engines - for various different engines supported by the FDMs

In progress

  • FDMs - for various FDM configs that are supported (Isix)
  • Views - for aircraft-specific views (Isix)
  • Splashs - for aircraft specific splash screens (Liam, final)
  • Animations - for aircraft (asdfasdf)
  • Liveries - for livery-specific textures (Liam)

To do

  • Panels - for 2D/3D cockpit panels (maybe categorized into 2D/3D?)
  • Instruments - for aircraft specific instruments (possibly with its own Textures subfolder)
  • Sounds - for aircraft specific sounds
  • Systems - for systems such as the electrical system
  • Nasal - for aircraft specific Nasal scripts
  • Docs - for aircraft specific documentation
  • Huds - for aircraft specific HUDs
  • Resources - for all sorts of aircraft specific development resources that may be required by other developers to continue development of an aircraft (i.e. data, images, artwork etc) but that isn't officially included in any of the other folders because it isn't yet used. That is, such "resource" folders could/should be automatically excluded from the script that is currently used to create the default base package for distribution.

Extras that should be completed:

  • README
  • HELP
  • FEATURES
  • TODO
  • AUTHORS
  • CHANGELOG

Authors

Liam finished the 3D model, liam.gathercole at gmail dot com Isaías V. Prestes, isaias at gmail dot com If anyone can complete any other aspects of the Model PM 'liam' or 'isix' in the Forums or email.