scott967

Members
  • Content count

    4,475
  • Joined

  • Last visited

Community Reputation

21 Neutral

About scott967

  • Rank
    Member - 3,000+

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    none
  • Virtual Airlines
    No

Profile Information

  • Gender
    Male
  • Location
    PHHI

Recent Profile Visitors

5,094 profile views
  1. scott967

    who stole the plane

    Meanwhile, a corporate pilot in New Mexico took off in the company plane and flew it into his house (per news reports). scott s. .
  2. scott967

    Froogle's take on FSW and possible impact on P3D

    I'm not sure I understand the legal theory behind such a suit. LM has an agreement with MS to use MS's property or rights. A violation would seem to me to be between those two parties. I don't see how a third party has standing to complain about how the grant of right is handled. I could see maybe Dovetail has a potential issue with MS if MS made representations about what MS would or would not do. scott s. .
  3. scott967

    Southwest Accident

    NTSB pictures: https://twitter.com/NTSB_Newsroom scott s. .
  4. scott967

    Deducting cost of flight simulation...

    If it's an employee business expense better grab it in 2017 as it goes away for 2018. Note that you only can deduct expenses that exceed 2% of your AGI. If you are self-employed, independent contractor, single person LLC etc you have more latitude, but you have to show you have a profit motive and not a hobby. scott s. .
  5. scott967

    Daylight Savings Time Not Updated

    I've posted this in the past, but I like to think of the sim as having two phases: setup and run. In the setup phase the sim determines UTC (GMT) by using your settings and default flight to convert a "local" time into the corresponding UTC. If the conversion results in a "wrong" UTC (for example, you want UTC to be "real world", then adjusting the time in your flight setup is needed. If you want it to happen "automagically" you need to select a default flight that has the needed difference between actual local time and UTC. Once setup phase is complete and the sim starts running, UTC is used to determine local time based on scenery files. Those files just correct the local clock. The astronomical events (such as sunrise / azimuth) are always correct for UTC. scott s. .
  6. scott967

    DST in P3D

    Don't have P3D, so unless they have made some changes in general if you set UCT to correct time, the world will look correct, though the local time shown may be off. To get correct local time you need scenery files to depict the time zone boundaries and also temporal variations (DST), otherwise you get the default longitude-based timezones which were incorrectly assigned by MS. Unfortunately, the scenery sdk only allows you to create rectangular lat/long-aligned regions to apply specific time-zone definitions to. So to create a real-world timezone boundary you have a variation of fthe "packing problem" -- how to create a minimum set of rectangles to represent an arbitrary shaped region with a specified maximum error (and also you need to have adjoining timezones match with "holes" or you get strange jumps in local time as you cross the boundaries). I could never find an algorithm to do this so it was all "by hand". Then, there was a bug that the sdk provided for "priority levels" for the timezone rectangles so you could in theory overlay rectangles to fine-tune the coverage, but I found that the priority levels weren't consistently applied in the sim and I could never figure out when they would or wouldn't work. Makes it hard to manage areas like the north border towns of Mexico that follow US DST, while the rest of Mexico follows Central America. Then of course if you set your year back you would need to have the appropriate timezone as in effect in that year. The master "Olson" timezone database can be used as a reliable reference and it would be better if the sim simply referenced it rather than creating its own. scott s. .
  7. scott967

    Scenery in SSD disc?

    Of course it is feasible, but in 2018 I would simply get a bigger or second SSD. I think the easiest way to move stuff to a new location is to move an entire folder tree to the new location, leaving just an empty (top level) folder in the original location. Then create a symbolic link from the new location to the old, empty folder. There's a freeware program out there called Junction Link Magic v2 that makes it easy to do, or you can use a command line. When you do this all programs look for files in the original location and the OS translates the path to the new location. scott s. .
  8. Hawaiian was always a DC-9 shop for interisland, while competitor Aloha was 737-200. I think Hawaiian preferred the cockpit design / rating situation as they upgraded the fleet through MD-80 to the 717. Hawaiian flew B-767 on mainland/Asia flights but has phased out Boeing for AB 330. Now they are taking delivery of AB 321NEO for smaller capacity flights to the west coast (to compete with the 737 ETOPS operators). There's some rumors SouthWest may attempt to enter the interisland market. No one has been able to beat Hawaiian at it (either went broke or gave up). Midwest I think was in the same situation moving DC-9/MD-80/B-717. scott s. .
  9. scott967

    United says "Aloha ‘Oe 747"

    United recreated its first 747 pax flight KSFO-PHNL as its final flight. Info here: S-A article and here: HNL Rarebirds. scott s. .
  10. scott967

    Waypoint Locations

    Take a look here: http://www.aero.sors.fr/navaids3.html scott s. .
  11. scott967

    magnetic variation question

    Haven' looked at it lately, but FAA practice was to use "epochs" which are refigured every 5 years (and then a model is created to allow calculating expected variation for any given date). FAA analyzes the change of the upcoming epoch when doing chart revisions, and if the difference is larger than a certain amount from the epoch used in the current chart, it updates the chart accordingly (I think the delta is as large as 10 degrees). So for example the localizer course shown on the chart is generally not going to be a compass heading. Same thing with VOR, with the added complication as described before the problem of "rezeroing" and certifying the VOR. scott s. .
  12. scott967

    ILS reception range?

    In the US, the FAA defines a standard service range of 18 nm and this is the distance to which flight standards inspects and certifies the ILS. In some instances an extended service range is defined and certified. In Europe the standard range is 25 nm. The actual signals can be received at longer range depending on terrain, but aren't certified. scott s. .
  13. Aircraft can either rely on data provided as part of the aircraft addon, or on whatever data is in FSX. Ideally, they match 100%. The problem is, many simmers want to use "real world" data, and they constantly update the aircraft addon data. Thus there is a delta between the two sets of data. It is feasible to update FSX or P3D to current "real world", but the way the data are structured as part of the scenery database, it isn't as easy as you would want. So you have to decide on what trade-offs you are willing to accept. The first priority probably should be the visual scenery, since flying to non-existing runways and taxiways kind of kills the buzz. That means getting addon airports where you are going to fly. One big advantage that didn't exist when FSX was released is now most air navigation is based on GPS lat/long positioning instead of the old "rho-theta" that was harder to convert into FSX-compatible data. scott s. .
  14. scott967

    Driving versus Flying

    The wild card is if you don't hold an IFR endorsement and the weather. scott s. .
  15. scott967

    Passenger dragged off overbooked United flight

    As expected United Pilots union wants to separate themselves from actions of Republic and its pilots (though other than DHing, Republic crew seem not directly involved). We have a somewhat related incident here at PHNL recently. Airport is operated by the state and they contracted with state sheriffs for "policing". At some point (local media haven't followed up yet) a private security company (dba "Securitas") was contracted to provide "some" duties and there seems to have been accretion of duties, such that now at least some employees carry firearms and dress with "uniforms" with "POLICE" on the back (undoubtedly to solicit compliance with whatever "order" the employee gives). one of these "POLICE" shot and killed the dog belonging to an arriving PAX who had uncrated the dog and was waiting outside PAX terminal for pickup. Circumstances behind the shooting are under investigation, but the pertinent part is the use of persons with unknown training/accountability as "POLICE" (so-called). scott s. .