Well done for the new idea of management, MFA!

I just feel like I wanna shout... MFA, YOU'RE IMPROVING IN UR MANAGEMENT, finally!

Thumbs up for it!

Well, before this, MFA seriously gave me damn damn damn lotsa of troubles. In order to search for a PEACE, I've to "swallow" down lotsa unsatisfaction and solve the stuffs quietly. Unfair, but ought to.

Nevertheless, I'm glad. I'm really glad that they come out a brand , real good idea. I don't know whose idea is that and belong to which copyright for that idea, well, that's not my business. I'm just glad to see it being apply to this MFA.

In 2010, MFA is taking a new batch every 8 weeks SHARP! Because of this, a academy which already has backlog, slowly become more and more crowded. BACKLOG + CROWDED = EXTRA DELAY! A company which only works 5 days per week stands no way to handle ended up those batches which having backlog, will fly on Saturday. Good idea for...solving; poor idea for...junior batch which facing backlog more like no flying on Mon-Fri but only flying on Saturday.

Latest update... flying instructors will be working 5 days per week. Flight operation will open 7 days per week. So who is going to duty/work for that 2 days? Answer is...Each instructor will be having a different OFF days. Some are having Mon-tues, Some Tues-Wed, some Wed-Thurs,.....
Problem for jaga-ing(taking) the flight ops without paying extra in their pocket salary...SOLVED!

Students who under their own instructor will follow the same off days as well. So...
Problem for the backlog will reduce when in each day, only specific and limited students will be flying. No more "hijacking"/"grabbing"/... the aircraft. aircraft to student ratio ... OK~! Problem 2 ... SOLVED!

A company which can operate 7 days continuously... Yea..facing extra electric and water bills. Well, if new batch keep coming in, seniors keep going out, hostels be check in and out, profit is more than enough to cover the bills! It's much better than stucking seniors in and on hold new the new batch. Problem 3 in gaining profit... SOLVED!

and still got many more...

Anyway, I sincerely thumbs up for this solution. Though it's a bit hard to adapt especially those use to have Saturday and Sunday as the weekend. Well, this is pilot life and this is just a small OFF DAY changes be made.

Cons... please make sure ya having an idea to settle the cafeteria side in a system way. Guess "he" doesn't wish to have a chaotic scenario happen other than flying part.

Thumbs up for the management way from a company and students ' side!
Well done, MFA!

NTSB for today:

NTSB Identification: MIA06FA039.
The docket is stored in the Docket Management System (DMS). Please contact Records Management Division
Accident occurred Sunday, January 01, 2006 in Grand Ridge, FL
Probable Cause Approval Date: 12/20/2007
Aircraft: Robinson R44, registration: N442DH
Injuries: 3 Fatal.

The commercial pilot was ferrying a helicopter with two passengers/friends under Title 14, CFR Part 91 when the helicopter collided with trees and terrain in a wooded area at night, in instrument meteorological conditions. Witnesses related that the helicopter had landed near a hotel and truck stop, and the pilot and passengers had inquired about renting rooms. The pilot and passengers elected not to rent rooms, but walked to the truck stop and had a meal. After the meal, the helicopter was seen departing to the south. The helicopter did not arrive at its destination, and a search was initiated. A witness in a car on a nearby freeway, about 6 miles from the truck stop, reported to the local sheriff's office three days after the accident, that he had seen an explosion south of the freeway the night of the accident. Searchers located the helicopter in thick woods, in trees about 60 feet tall. The wreckage was extensively fragmented, consistent with a high speed impact with the trees. An on-site examination of the helicopter disclosed no evidence of any preimpact mechanical anomalies. Weather in the vicinity at the time of the accident was reported as 300 feet overcast, visibility 1.75 miles in mist, with thunderstorms nearby. The pilot did not have an instrument rating, and the helicopter was not equipped with instrumentation for flight into instrument meteorological conditions. Toxicological samples from the pilot disclosed extremely high levels of methamphetamine. Methamphetamine is a rarely prescribed drug, and its use is not approved for pilots. Methamphetamine is highly addictive, and is most widely used as an illegal recreational drug. The amount of methamphetamine in the pilot's system was approximately 50 times higher than expected from a single dose of a prescription drug. Use of methamphetamine can result in marked personality changes, psychosis, irrational and impulsive behavior, irritability, hyperactivity, and other symptoms.

The National Transportation Safety Board determines the probable cause(s) of this accident as follows:

The pilot's continued flight into known adverse weather, and his impairment, which resulted in an in-flight collision with trees and terrain during cruise flight.

this is actually the blog continuos of xiuyu88.blogspot.com :)

Yesterday I came across to a conversation before I departing back to my hometown.
"Where's the blog which is pink background? I was your reader before joining MFA"
"o.O Mmm.. I see. Thanks."

another conversation of...
"Didn't you know her? Especially her blog. Famous kut(Bahasa Malaysia)~ We're friend from there."

Further conversation
"I accidentally found your found online when i was searching for my stuffs. I confirm it's you. I'm reading it half way. Now got to fly. Will continue the post later on"

From there..., I've decided to shut down(more on setting it as my personal blog dairy) the xiuyu88.blogspot.com
Sorry. My honesty and direct in speaking, somehow I'm afraid it will bring me disaster in the training life and offense too many people indirectly. That's made up the final decision to stop that blog be published publicly.

When I checked back, the gauge still can track out hundreds people out there clicking my ex-blog daily. If you had the fate, here will the blog.

I didn't notice they're so many people reading it actually.

Guess my previous blog has made me be "slight famous" among those pilot wannabe until they are in the flying academy. Well, I have set it to private blog due to many private(my dairy) posts were in. This blog will be the continue blog of the www.xiuyu88.blogspot.com that any of you used to be reading it. It will still be the same. Noooooo worries~ ;)

Lets have the next NTSB report for the cause of accident to increase the situation awareness :

NTSB Identification: ATL06FA030.
The docket is stored in the Docket Management System (DMS). Please contact Records Management Division
Accident occurred Sunday, January 01, 2006 in Peachtree City, GA
Probable Cause Approval Date: 4/25/2007
Aircraft: Piper PA-28-180, registration: N2169T
Injuries: 1 Fatal.

The pilot requested the localizer 10-approach to the Macon Downtown Airport, Macon, Georgia (MAC). The pilot was radar vectored to intercept the localizer, and cleared for the localizer 10-approach. Shortly thereafter, the pilot advised approach control that he had over flown the localizer. The approach control specialist issued vectors back to the localizer, and he was cleared for another localizer 10-approach. The pilot reported to approach control that he was having trouble staying on the localizer, and requested to go to the Middle Georgia Airport, Macon, Georgia (MCN). He was subsequently cleared for the ILS runway 5-approach to MCN. The MCN tower advised approach control that the pilot had panicked during his approach, and went missed approach. The pilot contacted the MCN tower, reported that he had lost the localizer, and requested if he could be taken around to do the approach again. He was issued radar vectors back to the ILS runway 5-approach, and about one-half mile from the approach, the pilot requested to come around for another approach after drifting off course. The pilot made two more attempts to land at MCN before being radar vectored to the Peachtree City Airport-Falcon (FFC) localizer 31-approach. During the approach into FFC, radar contact was lost with the airplane. The airplane had collided with trees about 1 mile from the approach end of runway 31. Postcrash examination of the aircraft structure, flight controls, systems, engine, and propeller showed no anomalies. The pilot received his instrument rating less than 6 months before the accident, and had accumulated 17.1 total hours of actual instrument flight time. He had 133 hours of simulated instrument flight hours.

The National Transportation Safety Board determines the probable cause(s) of this accident as follows:

The pilot's failure to maintain sufficient altitude while performing an instrument approach in instrument meteorological conditions, which resulted in an in-flight collision with trees and terrain.

Wondering why there will be so many air crashes...

Sometime, I'm just thinking... what has made it to have so many accidents in a month? Pilots' fault or air crafts' problem or some other else?

When you're part of the members in aviation, especially as an aviator as known as a pilot, you do will come across a conversation of...

"Hey, you know?! XXX place gt XXX in trouble/crashed! XX person involved, currently..."

Everything can just happen in a second! I do wonder that when will be mine?! I admit that I did experience an engine quit in sudden with no reason before. Nevertheless, compare with many, it's just a small case to handle with in that kind of situation. For a much more critical one...when? Tomorrow? Next year? 10 years later...? Frankly speaking, the moment I heard all these cases, 1st few thing come to my mind is... : Are the pilot(s) OKay? What aircraft? From where and happen at where? What's the cause of it? Always, that 4 questions will catch my brain keep thinking. Well, learn from the mistake. To be exact, LEARN FROM OTHER PEOPLE MISTAKE! I do and never wish it will really happen to me. Maybe one day it will, and I do hope by that time it happen, I'm always ready to face it with calm.

I remember in aviation conversation, my friends and i came to the same view...
"Plan to the worst as you can never expect will happen for the next second"

It's freaking true. Be a pilot, you're always need to be ready with Engine failure/Power lost, engine on fire, Bird strike, Electrical failure, Alternator failure, Suction failure, Circuit breaker pop-up, Extremely bad weather, ...... etc. Anything you be able to mention in the aircraft, it will have its tendency to get malfunction. Even you have planned for a Nav., you'll need to plan "outside" than you routes for in case/emergency. You may not know that the runway is closed for temporary/the weather is bad enough and you need to hold/ you're required to divert/ your passenger isn't feeling well/... Always, that's the worst scenario has to be plan. Not only check for the destination aerodrome but to check with the aerodrome which may pass by/abeam/the nearest. Understand its plan view, length,... A lot. That's where a COMPLICATED flight can be brought up.

Recently I've been heading my head in NTSB (National Transportation Safety Board). Though I've too many stuffs on queuing, somehow, I still wish that i can spend some time to read up what had happened in the past air crashed which NTSB be able to investigated/pointed out. Understand the summaries can bring the help in more awareness.

I'll try my best in posting in each post... or reader(s) can also actually obtain it from NTSB website.
"
NTSB Identification: ATL06CA031.
The docket is stored in the Docket Management System (DMS). Please contact Records Management Division
Accident occurred Sunday, January 01, 2006 in Phenix City, AL
Probable Cause Approval Date: 3/28/2006
Aircraft: Piper PA-23-160, registration: N4370P
Injuries: 1 Serious, 1 Minor, 1 Uninjured.

The private pilot was on a visual flight rules cross country flight when he began encountering instrument conditions. The pilot continued into the instrument conditions for about 30 minutes before asking Atlanta Approach Control for directions to the nearest airport for landing. The controller directed the pilot to two different nearby airports but both were below minimums. The pilot informed the controller that he was low on fuel and needed to land as soon as possible. The controller directed the pilot to the Columbus Metropolitan Airport, Columbus, Georgia. The pilot told the controllers that he would attempt an Instrument approach. The pilot attempted four unsuccessful approaches with the controllers talking him through each approach. On the fifth approach, at five miles from the runway the pilot stated that both engine's quit due to fuel exhaustion. The pilot called "mayday" and during the forced landing the airplane collided with trees and the ground separating the right wing, half of the left wing, and coming to rest inverted. The pilot did not report any mechanical deficiencies with the airplane during the attempted approaches.

The National Transportation Safety Board determines the probable cause(s) of this accident as follows:

The pilot's inadequate decision to continue VFR flight into IMC conditions, which resulted in a loss of engine power due to fuel exhaustion."

** Learn from other people mistake ; Learn the emergency procedures by heart and always prepare to face the worst scenario. =)