From Airlineapps website:
*PIC = PIC + Instructor
*Total = PIC + Instructor + SIC + Dual
*Rotor time IS NOT included in any total time calculations.

"Dual" is where I put the hours I can't log as PIC but is not SIC either. At least it counts toward total hours and isn't thrown away.

 

This happened a lot with me in the T-34. I just assumed if I was the designated IP (the one giving an event, even if it was with another instructor), aircraft commander (signed for it) or solo, it is PIC time.

If I was receiving training (recurrent, Stan check, etc) or otherwise wasn't sure, I counted it as dual received.

In the end, if you can logically explain it and are consistent, I doubt it will matter. Most mil guys, especially training command instructors have enough time in each category that it isn't an issue.

 

Yeah, to be safe I could just split all those CT flights 50/50 IP/Student and be legal. It's probably less than 10% of all my hours, certainly not worth raising questions. It would move me from like 2500 PIC/IP and 600 dual/student to 2300/800 ish. I figure the hours get me the interview and the interview gets the job, I'd be amazed if those hours in question made a difference either way in getting me the interview but I can see how they could lead down a rabbit trail I don't really want to be on once in the interview. Thanks for the inputs.

 

In both airlineapps and pilotcredentials, you need PIC, SIC, Instructor,Night, Instrument, approaches, landings, and sorties. You also need to break it out by aircraft and have a means of breaking out variously 6, 12, and 24 month currency. Every military service and flight community will have some specific challenges. Keep it simple. If you are incredibly anal then make a spreadsheet sortie by sortie with those columns and split your flight time accordingly. That was too much for me so I did it by month. When in doubt I rounded downward and to most conservative interpretation. For example some commands broke down flights by sortie, some by days, and some by mission over the years. So on a 7 day mission where only flight times and landings/approaches were listed, I only assumed a sortie a day. Sorties drive the military conversion factor that is automatic in both application sites too so YMMV. The flight times do 2 things, get you over the minimums to get in the game and can be reviewed in the interview. Only SWA makes a big deal of your logbook. The others looked at military logbooks or printouts and were fine with it. Hint: They also really liked my generic excel breakouts of the times.

Good luck.

 

After advice received here I dumped my sortie count and hour distribution and started over. For the most part my general estimates were pretty close; however, they might have led to some discussion and I'd rather not be talking about my log book during an interview.

I ended up going line by line for all my T-37 and T-38 time after getting my local IP certifications (everything prior to IP cert assumed student time unless solo). If the time was split IP/Primary, I called 100% of the logged primary time (mil) as student time (airlineapps). If the time was primary only, I know I was solo and called it PIC. The IP time is already broken out and didn't require any additional action on my part.

Previously I'd lumped all my solo primary time with my IP/primary time and then applied conservative assumptions about PIC vs. student. Lucky for me, it turns out I've done more solo flying than I thought so in the end I actually increased my PIC time. My overall PIC/IP sortie count vs. student suffered just a little bit, but overall I'm glad that I spent the time to properly sort this out.

 

That all seems pretty logical. I'd be surprised if any of that created issues for you in an interview.

 

Mike, i would print out your explanation and affix it to your logbook.....